You like the one sane thing systemd does - very few folks argue that it's implementation of unit files and friends is a bad thing. Other init systems were prog

You like the one sane thing systemd does - very few folks argue that it's implementation of unit files and friends is a bad thing. Other init systems were progressing in the same direction though. The problem is everything under the hood. Have you ever tried to debug a wedged Linux server with a somewhat esoteric startup issue these days? It's exceedingly difficult, and not simply because you need to learn an new tool chain. It's simply made many things opaque and replaced other bits no one sane would ever expect (e.g. having to remember systemd re-implements 'rm' and the quirks that brings, etc.) As a cranky systemd-hater I also love the unit/service files - they work great, and as you say one tool that does it well. And systemd excels at making any random program a reliable and standardized daemon. Why does it also need it's own dns resolver? If I were simply an end-user or developer making apps to run on linux I'd love systemd. It's when you're maintaining the bare metal where you start to see it's lesser known and more ugly parts.