Comment Re:My opinion on the matter. (Score 1) 826
My story: Been using Linux and BSD heavily since the 90s. I don't really care if you spell "restart foo" as "/etc/init.d/foo restart", "/usr/local/etc/rc.d/foo.sh restart" "service foo restart", "systemctl restart foo", or just "pkill foo && foo". As an end user of the init systems, those are fungible.
As a developer of things that uses the init systems, there's a huge difference. SysV and BSD inits are close enough in functionality that if you learn one, you can pick up the other. systemd changes that totally, in ways that many of us aren't convinced are actually better. I love learning new stuff! I just changed jobs to learn new stuff! New stuff is cool... but only as long as there's a reason for it. I don't see systemd as being advantageous, at least on the server machines where I spend my days.
I'll be happy to pick up systemd if and when 1) there's no alternative short of maintaining my own private Debian fork, or 2) I can see a reason I'd want to rip out the tried and true, Unix-philosophy-conformant "do one thing and do it well" init systems we have today. As of this moment, systemd seems to do way too much. Given that it's a single point of failure for an entire host, that makes me distrustful.