And more importantly SysV literally consists of the shell commands that get run, which is a huge win for debugging. The more declarative systems all themselves eventually turn into a bunch of imperative exec calls, but you can't see them (runit may be the closest to keeping the visibility of sysv). And, I mean, I really love GNU shepherd but at 3am with a boss yelling at me I really just want the actual shell commands being run.
Except that you will get that 3am call every night with such a system, while systemd can actually handle failures properly with proper retry strategies, no concurrency problems, etc. And any failure will be local to a service, not the whole system state.
I mean, no? I spend a lot more time fixing init problems now than I did 15 years ago. It keeps me employed, so yay, but it's just annoying to have consistent problems I didn't previously have.
