I've often heard people saying that systemd attempts to do too much and as a result is bloated, but personally i've found it to be sufficient for what i want to

I've often heard people saying that systemd attempts to do too much and as a result is bloated, but personally i've found it to be sufficient for what i want to do - making certain software run and/or automatically restart on a server. Some of the alternatives that i've heard of: - SysVinit (i think older RPM distros used it) https://wiki.archlinux.org/index.php/SysVinit - OpenRC (i believe that Alpine Linux uses it as its default) https://wiki.archlinux.org/index.php/OpenRC - and here are some other links https://alternativeto.net/software/systemd/ For better or worse, i've mostly just stuck to using systemd because it's good enough - and init systems that require scripts to be written manually intimidate me, since it seems like it'd be easy to make mistakes and the scripts wouldn't be standartized enough. Personally, i prefer to create a configuration file that just defines where the software is, how to keep track of its PID, where and how to get configuration for it, as well as what user/group to execute it as (among other things). Maybe the poster you're replying to will provide some arguments against systemd and situations where it isn't very nice to use.