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’ll also add that systemd is so different and confusing that even Red Hat’s own training team teaches things wrong. If you take the new RHCSA on RHEL 8 they have a section where you have to create a container and have it running. systemd’s design indicates that this SHOULD be a system service so should create a unit file and set the User= to run it as a user. Instead they have you log in, run it as yourself, and then enable linger on loginctl to prevent your user from logging out. That is WRONG according to systemd’s design and since that’s outside the design there’s a chance in the future that something will break that. Or better yet, if your application is there running and you go to shutdown your system, systemd probably won’t stop it correctly and it could cause data corruption.