

Tech companies hoping to keep certifications that allow them to get customers do not “move fast and break things”. This kind of ghetto process should definitely hurt business.
For instance: at my day job where I tech-whore to big ents and govs, about 10% of our time is spent only in meetings where we review what’s happening and how: and that kind of transfer would have a schedule, stakeholder sign-off and listed processes to follow and review. There’s post-incident reviews and follow-ups in case of the slightest deviation or surprise, and the process is refined each time. That kind of sloppy work wouldn’t survive.










Oh, but it is. Upstart and sysV will both assassinate everything after a point. This bullshit is entirely new, either by Systemd sucking, or Systemd allowing this shit (thus, sucking), where neither thing happened beforehand.
I admit I rage when it’s starting or stopping and can’t win for all the losing – especially because “startup time” was the the main (unfounded) feature on the banner they waved around.
I work with sysV and Systemd and shut each down on a. Regular basis, via tooling, for stuff like patching, so it’s often a horse-race to offline. The difference is often negligible, for new machines or established boxes with apps, and the main difference is sometimes Systemd fails its YOU HAD ONE job from time to intermittent time.
I work in a team where Unix and Linux is ~15 very experienced admins, so don’t fret over the skills and experience question or the scale question.