Debian reconsiders init-system diversity

I think you missed the primary point of tlamp's comment: with systemd unit files, you can find out what depends on what, and many other details about a service *just by looking at a config file*.

With the old sysvinit way of doing things, you only had a global sort-ordering of scripts, and anything else you had to actually execute the script to discover.

Amongst other things, the config file approach gives you all the information you need to "easily" generate a sysvinit script and ordering (if you wanted to migrate in that direction) - whereas the opposite is basically impossible.

If we ignore all the rest, moving the ecosystem to systemd unit files (or something similar) gives us a much more useful description of our system.