@Cocoa@nekosat.work Yes. 99% of my init needs are met by running daemon[1] from rc.local at boot; the default method on Slackware. With three lines of shell script I get a named daemon, with PID file tracking, executed by its own user, optionally in a chroot, and with stdout and stderr redirected to log files.

And for the 1% when I want something crazy, like running multiple network namespaces for different services hosted in them, connecting over specific Wireguard networks each, and isolated from seeing the actual network hardware directly, I can modify the simple networking init scripts, and make it happen myself in a couple of hours. I don't even want to imagine what it would be like to try to modify systemd and NetworkManager code to add such a feature.

My experience with systemd was very buggy, in production, causing extended down-times, from bugs left unfixed for years. My experience with OpenRC was alright, but does not spark joy. Only caused production downtime once, due to a buggy interaction with consolekit2, but that's a track record roughly %600 times better than systemd already.

[1]: https://libslack.org/daemon/