Boycott systemd
I can't access that site because it returns 500 right now, but: Can we please get over it?<p>Quoting the "Unix philosophy" as the reason to keep things like they were 20 years ago is laughable. 
I want to get things done, and managing processes using init scripts and daemonization is pain. <i>Edit: I'v read the cached version now, and this assumption turned out wrong. The authors see a need to replace sysvinit.</i><p>The amount of bad and inconsistent init scripts, messy PID file handling, makeshift service wrappers, defective daemonization and logging workarounds is so much worse than having one place that will handle those ever repeated tasks.<p>I love that in recent years Linux (as in distributions) got an attitude and actively push things forward, without losing compatiblity to older software. Apple introduced launchd and nobody complained. We start to rely docker and all sorts of new approaches to manage our services and nobody complains. But init is somehow regarded as the holy cow noone is supposed to touch although everybody agrees it sucks.<p>Even if it's technically wrong: Unix as a platform is now Linux. Everything else is niche products, and we don't have to use the same init mechanism on Linux/BSD/whatever just because we can.<p>I have deployed the same software on Debian Linux, RHEL Linux and AIX and basically had to reimplement service management scripts for every platform to have the best possible result. How could this get even worse?