Sure, but some of us have had Just Plain Bad experiences with systemd, regardless of startup scripts.
A server (running Debian Stable) I was rebooting for a kernel upgrade wouldn't reboot -- it just hung at "Reached target Shutdown" (similar, I believe, to this bug
). Of course, it had already stopped sshd, so I had no idea what was going on until I dug out a monitor and plugged it in.
Another server had an entry in
/etc/fstab for an external USB disk that was occasionally used. One time after upgrading, systemd decided that, because the disk wasn't plugged in, it would just hang there because it couldn't mount an fstab entry.
Another time I go to turn off my computer and...it just hangs there, telling me the system is powered off (I had to physically turn off the power, though of course everything was cleanly unmounted so not a problem).
Yes, some -- or maybe even all -- of these problems can in part be blamed on me. The first one could be fixed with "systemctl reboot," the second one with "noauto" in fstab, and the third with "poweroff" instead of "halt." But that's not the point. The point is, when my *completely working system* decides to stop working on numerous occasions, and it can all be traced to one source, it just Isn't A Good Thing in my opinion. To each his own, though.