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 am for most part quite happy with it. For all the complexity it brings, it also allows you to do a lot of stuff easily and reliable that would have been a nightmare with previous systems.
My biggest nitpick is that some commands are needlessly obtuse, e.g. trying to find an error message in
journalctlis a mess when you aren’t already deeply familiar with the tool. It will show you messages that are months old by default, will give exactly the same output for typos in the unit name as it will for no error messages and other little things like that.