I don't have anything against systemd that is until I tried void linux for the first time. The working of runit seemed very simple and efficient compared to the complexity of systemd.
I still don't hate systemd, but I just wish it was simpler.
And most importantly you don't have to deal with things like environment variables or other session state leaking into your startup scripts as you had with all the init script based init systems.
I seriously do not miss services that worked when starting them from an ssh session but did not work on startup (because e.g. PATH had fewer directories).
I don't have anything against systemd that is until I tried void linux for the first time. The working of runit seemed very simple and efficient compared to the complexity of systemd.
I still don't hate systemd, but I just wish it was simpler.
To be honest
systemdis much simpler to me. Create a unit file, define what it depends on, accesses, etc. And you are done.And most importantly you don't have to deal with things like environment variables or other session state leaking into your startup scripts as you had with all the init script based init systems.
I seriously do not miss services that worked when starting them from an ssh session but did not work on startup (because e.g. PATH had fewer directories).
That too. I completely forgot about that.