>As cluttered and dated as SysV is at least you don't have to take pieces of it apart to change what flags are being used to call some secondary command at boot time.
And that may be touching on a big issue. sysv en its like was created in an era where you could not easily spin up another server as needed, and doing a full reinstall for a "minor" issue was seen as insanity.
Thus systems that could be fixed in place, with minimal tools, where the order of the day.
Now however we have a generation that has grown up accustomed to doing reinstalls at the drop of a hat, thanks to desktop computers. And their server environment makes heavy use of virtual machines and containerization. Neither of these are conductive towards a mentality of fixing issues in place, never mind making sure they stay fixed.
In essence they are doing service uptime via machinegun, not belt and suspenders engineering. Who cares if a instance crashes, there are 1000s ready to take over, and it will be rebooted in seconds anyways.
Consumerism has reached the server rack...