SysV init is crap, but so is systemd as init process. One example is that an admin needs to know why the system does not boot properly. In this case the kernel messages help. systemd is not helping here.
I've currently one problem that I need to solve, but I need 2 people, one to make a video, the other to press Ctrl+Alt+Del to capture an error message that appears for 0,1s after sending the key sequence, when my PC does not boot. This is crap! Why the hell it does not boot occasionally, I have no idea and I've been an Linux/Unix admin for 25 years now. Why I cannot find it? Of course because systemd doesn't even log it!
This is brand new when systemd appeared. I loved to see the kernel messages to full extent...