Vehement systemd defence also overwhelmingly comes from hobbyists who have no real use for an init system anyway. In fact, this whole argument is crap, most hat

Vehement systemd defence also overwhelmingly comes from hobbyists who have no real use for an init system anyway. In fact, this whole argument is crap, most hatred of sysvinit comes from people who have never used it, is that a reason to discard all criticism of it? Of course not. I have had enormous issues with systemd, not when using it for desktop purposes, but precisely when using it for server applications. As an example, systemd can't handle a service which depends on a specific network interface (or specific bind address) before being brought up and the systemd developers blame the software for not listening to rtnetlink events or not relying on linux specific socket options[0]. This is unacceptable, it makes it incredibly difficult to run systemd on hosts connected to multiple segregated networks without lots of dirty tricks involving firewalls. [0]: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ https://www.freedesktop.org/wiki/Software/systemd/NetworkTar...