[jeroenhd]

systemd is far from perfect, but it's the best we've got on Linux. Treating systemd like an init system is like treating your car like a Bluetooth speaker: yes, you can connect your phone to the speaker system over bluetooth and yes you can take the speakers with you to most places, but the speakers are only a small part of what you're taking along with you

Nobody is forcing systemd down anyone's throats. You can use init.d if you like, or OpenRC, or whatever you prefer. What's happening instead is that people who maintain software are no longer interested in maintaing init.d scripts or working around the missing features many supposed alternatives lack.

[greatgib]

And to add to the fact that it was shoved down our throat, it wasn't even the best system. There was plenty of them that were interested with great features initng, upstart,... But systemd won because they manage to force us to depend on them for main distributions and core components like login. Pushed strong by red hat...

[adrian_b]

Sorry, but systemd is really forced upon the users throats, all the time, more and more.

Just a few weeks ago, in some systems that worked perfectly without systemd, I have upgraded Xorg server, but the new version would no longer run, because it has acquired a hard dependence upon systemd.

As a workaround, I had to run the additional elogind daemon, which does not provide any useful function, except of keeping happy the developer who has added this extra systemd dependency.

Such events have happened for years, every few months, with more and more dependencies of systemd added to various applications, which after that do not gain any useful feature but they force their users who do not want systemd to waste time for developing workarounds that satisfy the new undesirable systemd dependencies.