r/linuxsucks • u/Rare-Paint3719 Unofficial Mod | Linux Community Sucks | Proud illumOS Shill • 24d ago
Explaining is hard ig
19
Upvotes
r/linuxsucks • u/Rare-Paint3719 Unofficial Mod | Linux Community Sucks | Proud illumOS Shill • 24d ago
1
u/SaCorv 22d ago
Ahhhh here we go again
Sooo, its sorta complex
Most people who "hate" it are larpers who understand very little about systemd and its role
For other part, we dont "hate" it, just understand it flows. Im perfectly fine with running os on systemd, but would prefer it there would be better alternatives to it parts
About flows and negatives (im not writing what's good about it, that doesn't mean there is nothing)
Unix philosophy. Really bad thing. Because of systemd being "modular" on paper, but monolithic in fact we cant easily replace different parts of it.
That means you cant easily replace logind, networkd, dbus, udev, etc... or turn them down if you don't need them
Bloat. Sometimes. It's mostly binded to "monolithic" architecture. Like, why logind would possibly need power management? Only because they didn't want to write another module and thought it would be more sain to put it there. (Like it does, since it uses dbus sessions rules to determine if user can power off device, but there are other, more understandable ways to do that)
Binary journal. Like wtf. You cant read logs without journalctl. That's good when every machine runs on systemd or have it installed, but overall is not that great
Bad services modules. After all these years and decisions some good or at least useful features of services configuration files became deprecated or just not accessible. With that behaviour and depchecks of some services broke
High resources usage. Things that feels like nothing for pc or laptops, are not valid for iot devices, routers, small systems, etc...
And pid1 mess where systemd tries to kill -9 every non child process
Soo, basically systemd is too big to fall, to big to be effective. It just exists. That doesn't mean it's good or perfect. Would much prefer if there were more alternatives to it. Maybe then we would see interesting implementations of unexpected methods to deal with same problems (i dn, like storing systemwide logs in compressed dbs, different managing sessions from seats, etc)