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?
Why do people keep insisting on capitalizing it wrong? It’s systemd, all lowercase. Never has it been Systemd, and never has it been SystemD.
Lowercase when referring to the command, uppercase when referring to it as a project or a piece of software as a whole. “grep” is a command with certain behavior; Grep (or GREP) is a tool on Linux.
How does that sound?
There’s some reasonable overlap where you might mean one or the other, but to maintain that there’s no reason to make it uppercase?
Exhibit A: https://www.gnu.org/software/grep/
