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 think @[email protected] 's point should be thrown in as a #3.
The lead dev was an absolute dick. That fanned the flames of discontent. People that would have otherwise come around to what systemd was trying to do, dug in their heels and have been entrenched since. It didn’t help that Pottering was employed by Redhat. Eventually most of the feelings were overshadowed by what ultimately has become a better solution.
The systemd hate that we hear now is the reverberations of those internet arguments from years ago and a very small handful of people who probably still hate Pottering.
At the end of the day, people still have a choice of what they want to use, so if you think systemd sucks and is slow, then use something else.