SystemD is blamed for long boot times and being heavy and bloated on resources. I tried OpenRC and Runit on real hardware (Ryzen 5000-series laptop) for week each and saw only 1 second faster boot time.
I’m old enough to remember plymouth.service (graphical image) being the most slowest service on boot in Ubuntu 16.04 and 18.04. But I don’t see that as an issue anymore. I don’t have a graphical systemD boot on my Arch but I installed Fedora Sericea and it actually boots faster than my Arch despite the plymouth (or whatever they call it nowadays).
My 2 questions:
- Is the current SystemD rant derived from years ago (while they’ve improved a lot)?
- Should Linux community rant about bigger problems such as Wayland related things not ready for current needs of normies?
I make plymouth do the verbose mode because it’s cool and hacker-y. Also I like when it says “failed” and I know what failed. For a few weeks I kept having to manually start firewalld and I never would have known otherwise, update seems to have fixed that though.
Tbf, I really only have experience with fedora and thus systemd, so, I like it but I “don’t know what I’m missing” in a sense.