@hobbsc I believe @munin comes from a security orientation: PID 1 should do very few things: start your system, launch processes, kill processes, shut down your system, and a couple of others. Systemd is just too invasive for that role.
I'm personally uncomfortable with this, and with the way it suddenly conquered nearly every distro. I'm not otherwise against it, but I do intend to swap the family's VPS fleet to Devuan instead of Debian (have not found a non-systemd replacement for CentOS yet) pending consultation with the kids.
OTOH, whenever I've had #systemd on a computer or VPS from the beginning, I haven't had much of a problem. Switching from #sysvinit ("upgrades" by the distro), however has always failed, requiring a from-scratch reinstall to make the computer operational again.
@lnxw48a1 @munin @hobbsc Ironically, going the other way, from systemd to sysvinit, works just great. I recently transferred plateia.org from systemd (debian default on jessie) to sysvinit without any problems at all. I did end up copying proper sysvinit files from another box though, but even without that it worked just fine (I just like my pretty service status readouts, instead of just "UP")
runit works fine on CentOS, by the way. My linux partition is CentOS 6.8 with sysvinit replaced by runit. Works just fine.
@xj9 @munin @viciousviscosity I agree that providing alternatives is better. But providing the perspective "well, it shit right over me" is helpful if people think a thing is all roses.
@hobbsc @munin Systemd has a bunch of good ideas but the devs tend to have an attitude of "we own the init system, you will adapt to what we decide". Often the technical arguments behind their decisions have merit but they don't seem to be team players. I think it's that attitude that's putting a lot of people off.
Also, they take such a broad view of what the init system should do that even pro-systemd people like me become uncomfortable with it. E.g. tying stuff up with dbus, making cron jobs a task of the init system, the integration with journald.
@munin @hobbsc I'd just like to interject for a moment. What you're referring to as Linux, is in fact, Systemd/Linux, or as I've recently taken to calling it, Systemd plus Linux. Linux is not an operating system unto itself, but rather another free component of a fully functioning Systemd system made useful by the Systemd init system, shell utilities and vital system components comprising a full OS as defined by Lennart Poettering.