Systemd does indeed solve a real-world problem, namely that the whole mess of how to start processes and services had become unmanageable complex.
The heart of the issue, I think.
Linux init and rc scripts are simple to read, open, transparent, and easy to trace. Their software tools approach makes for easy component management. However they are not easy to write well.
I find systemd complex, dense, and opaque. Systemd offers more, a lot more, but at a big price. Its reach is vast (and expanding). It feels like a "Windows" style solution. Comprehensive, but daunting.
I really enjoyed the video. And the message I took away (and have always thought) is that "the whole mess of how to start processes and services" is
still looking for a good solution.
However you are completely correct about Linux (increasingly with systemd) dominating the commercial markets. Automated deployments and containerisation are just accelerating that. Everything else if falling by the wayside.
So I'm pretty sure that systemd
is already the solution in the commercial world. C'est la vie. It's what the proprietary vendors used to call "adding value"...