Comment Re:If systemd is so bad... (Score 5, Informative) 209
It's because it's a genuinely better way to manage system services.
It's faster. It has explicit dependencies which enables parallelism. It integrates cgroups natively.
It unifies service configuration language. This is the thing that many people say they hate about it. Rather than any executable being able to do whatever it wants there's a model for how to describe your service and the things it will execute.
The biggest problem with it is that it's not seamlessly compatible with existing init scripts. If you don't have any existing custom init scripts, then this doesn't matter. In my life I've only written a few custom init scripts, and in almost every single one of them I went looking for something like libdaemon to help me simplify certain steps. systemd integrates all of that stuff and puts it into one manual.
Ultimately the people that hate systemd for legitimate rather than cargo-cult reasons it's because they didn't feel like they needed all of the extra features and functionality that systemd offered, so the cost of migrating seemed like a waste of time to them.
I've recently had to make unit files for systemd and, compared to my experience doing init scripts to cover the same workload about five years ago, it has been an amazing experience. I have no interest in going back to the old way.