Why are you still using systemd?code repo for the outro (credit to iceyrazor):https://git.iceyfox.xyz/iceyrazor/daccfish- Find me elsewhere -----------Symlin...
As I understand, one point is that systemd contradicts with its completeness the Unix philosophy of KISS, small tools that serve only one specific task.
The other point is that the main developer, Lennart Poettering, is employed by “big tech”, now Microsoft (before: Red Hat) and thus has switched to the “evil site”.
systemd is a monolith in practice, despite what its advocates like to claim. You can’t run just a part of it under another init without doing extra patch-up work (see elogind). Whereas you can run just one GNU utility on top of, or even alongside, someone else’s implementation of that or other utilities (for instance, in parallel with a rust implementation that isn’t quite ready for the big time yet).
systemd also won’t work on anything except Linux. Older solutions also worked on BSD. That matters to some people.
And the issue was never just Poettering’s employers. He had a bad reputation in parts of the Linux community long before systemd—he was also the main force behind pulseaudio, which was shipped long before it was ready for actual use in the real world and remained in a semi-broken state for quite a long time afterwards. And he often comes across as personally obnoxious. Nothing like telling someone “I’m not interested in fixing your issues with my project” (except less politely) to get them to adopt your code.
Either you build a tool that works well with one OS or you build one that works poorly with several.
And it is not as if those other OSes are waiting for new cross-OS init tools: They either seem to be happy with what they got or want something tailored to their own features.
As I understand, one point is that systemd contradicts with its completeness the Unix philosophy of KISS, small tools that serve only one specific task.
The other point is that the main developer, Lennart Poettering, is employed by “big tech”, now Microsoft (before: Red Hat) and thus has switched to the “evil site”.
Why don’t they hate GNU then?
I understand you aren’t one of them, but systemd is not a monolith.
Also, what’s so special with UNIX philosophy.
I hope they also hate proton, all browsers and the kernel, since those are also developed with help or by big tech
systemd is a monolith in practice, despite what its advocates like to claim. You can’t run just a part of it under another init without doing extra patch-up work (see elogind). Whereas you can run just one GNU utility on top of, or even alongside, someone else’s implementation of that or other utilities (for instance, in parallel with a rust implementation that isn’t quite ready for the big time yet).
systemd also won’t work on anything except Linux. Older solutions also worked on BSD. That matters to some people.
And the issue was never just Poettering’s employers. He had a bad reputation in parts of the Linux community long before systemd—he was also the main force behind pulseaudio, which was shipped long before it was ready for actual use in the real world and remained in a semi-broken state for quite a long time afterwards. And he often comes across as personally obnoxious. Nothing like telling someone “I’m not interested in fixing your issues with my project” (except less politely) to get them to adopt your code.
Either you build a tool that works well with one OS or you build one that works poorly with several.
And it is not as if those other OSes are waiting for new cross-OS init tools: They either seem to be happy with what they got or want something tailored to their own features.