Post #1562327
2026-03-31 18:27 UTC
* only systemd *or* any other init/service manager can exist in the same repo (some distros try hacks with shims and wrappers)
* that and software-side dependencies (a design "flaw" in the service manager part) forced popular distros to Systemd and they can't get away
* runs only on Linux and a very limited set of architectures
* not-invented-here and scope creep (debugging dns issues radicalized me against Systemd)
* design faults as a "integrated service suite" (doing init and services in one), leading to more critical vulns than all other init together
* unpredictable service run order, together with shitty logging
Stuff like that.
Edit: yees, Gentoo & co. support Systemd *or* Openrc. But that one is mostly service management and was designed as a drop-in, doesn't count.
The sad part is, some of it's nicer new features create further dependencies, won't get implemented in a independent way.
Replies (1)
-
@Specter@piefed.social 2026-03-31 20:19
Thank you for the thorough technical explanation, it is clear there are challenges for devs and I understand why the pushback exists now. As an end user these are things I haven’t felt, are essentially invisible to me so I never felt the need to run away from systemd. Thanks again.