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 believe a lot of people hating on SystemD are using the fact that it’s not really compliant with the Unix philosophy (one tool, one job). I like it a lot and it makes things much easier to manage, especially when you compare it undocumented legacy UNIX stuff. (That’s part of my job and it’s painful). I can understand the fear of feature-creep that might make it bloated down the line (stuff like homes for instance). But so far, it’s doing a good job.