Systemd lead developer Lennart Poettering has posted on Mastodon about their upcoming v256 release of Systemd, which is expected to include a sudo replacem...
As far as I remember Poettering worked for IBM’s RedHat for some time and then the systemd lobbying vibe became stronger (with Fedora being the RedHat toy). Nowadays Poettering works for Microsoft, btw.
Because the software he writes starts out good, and solves problems. systemd is a really nice initd replacement. Pulseaudio really improved audio on Linux. Distros adopted them because they were good.
The problem is feature creep, exactly like the OP post. For some reason, Poettering’s projects can’t contain themselves to a problem space. Converting init systems is a lot of work, and even if Debian had recognized the feature-creep of systemd as undesirable, there was no way they were going through all of the pain and suffering of another migration. Plus, there isn’t yet a clear successor to systemd. My money is on dinit; s6 is simply too complex, and has too many commands to remember. But the point is, systemd was an excellent initd replacement, and there was a lot of adoption when that’s all it was. And as it grew, distros were already committed and stuck with it (although, journald was there from the beginning, and that should have sounded warning bells).
As far as I remember Poettering worked for IBM’s RedHat for some time and then the systemd lobbying vibe became stronger (with Fedora being the RedHat toy). Nowadays Poettering works for Microsoft, btw.
How did he get so much influence over most mainstream distros? Asking for a friend…
he never, distros adopted systemd because it works, no one forced them, end of the history
No, that’s too rational. What leverage does he have on all of these distro maintainers? Someone needs to get to the bottom of this! /s
lmao found one answer exactly like that
Because the software he writes starts out good, and solves problems. systemd is a really nice initd replacement. Pulseaudio really improved audio on Linux. Distros adopted them because they were good.
The problem is feature creep, exactly like the OP post. For some reason, Poettering’s projects can’t contain themselves to a problem space. Converting init systems is a lot of work, and even if Debian had recognized the feature-creep of systemd as undesirable, there was no way they were going through all of the pain and suffering of another migration. Plus, there isn’t yet a clear successor to systemd. My money is on dinit; s6 is simply too complex, and has too many commands to remember. But the point is, systemd was an excellent initd replacement, and there was a lot of adoption when that’s all it was. And as it grew, distros were already committed and stuck with it (although, journald was there from the beginning, and that should have sounded warning bells).
don’t use the features, lol “nooo how dare them put new optionals features 😭😭”
As far as I remember Poettering worked for IBM’s RedHat for some time and then the systemd lobbying vibe became stronger (with Fedora being the RedHat toy). Nowadays Poettering works for Microsoft, btw.