Re: Hasn't this happened already with Upstart?
Now John this
"So just use syslog, like the default Debian install of systemd does."
is condescending, and ill-deserved. It's like telling a pilot who wants to go to the moon to "just build a rocket and go like NASA did". Sys admins and businesses are looking at spending time and money figuring out how to undo Mr. Pottering's good intentions, why is that? If systemd was truly a drop-in (transparent) replacement it would cause no angst (although I'm sure SOMEONE would complain).
However, now that the deed is done it's all going to come down to money, the question is whose going to get that money? Will I absorb the cost to change everything and allow systemd to infiltrate my servers going forward, or should I freeze everything where it is and put resources into an alternative distro like Devuan. I have to ask: "Does systemd brings any tangible or financial benefit to my server environment and business operation"? So far the answer is "no".
Perhaps systemd can improve desktop PC boot-time, but so can using an SSD, which truly IS a drop-in replacement; but even THAT no longer matters as many desktops here are virtual and up 24/7/365 (except the Windows VMs, they seem to need rebooting to remain stable).
Keeping on track with who gets the money, GNOME 3 is out, as is Windows 8 and the future Windows 10. Our users liked Gnome 2.x and it worked well, so Mate gets our support (yes financially) as does Windows 7 (but far less-so). We don't encourage Windows because with the exception of a certain nameless accounting package (that we're working to replace), it really is irrelevant and just increases costs.
We were set to start sending funds to CentOS but their implementation of BIOSDEVNAME and subsequent gushing about now being officially aligned with RH caused us to re-evaluate their strategic direction. It's not looking good for CentOS in our shop, although that too is subject to change.
In real-estate it's all about location, in system administration & business I.T. it's all about stability. We are always looking to improve things, but we need to do it in a sane manner. It's evolution vs revolution. If you change something critical, no matter how well-intentioned the change, you must QA & regression test it before releasing it. It has GOT to be ROCK solid, well documented, and transparent in it's use & maintenance. Miss ANY of these and you had best go back to the drawing-board.