Really why using systemd ? Honestly, it sucks.

I don't understand why so many people hate it. What else to use? Supervisor?

@retoor Same. It does it's job, so.... idk ¯\_(ツ)_/¯

People don't like it because it's bloaty and does too many things.

It breaks the UNIX convention of "do one thing well" that initd and earlier were better at.

It's perfectly fine though, people just like to bitch.

tbh i find systemd to be much more usable, intuitive and stable than init.d ever was.

@tosensei init.d was very simple, that was nice. Systemd has some nice features though.

I've never experienced stability issues with either to be honest.

@retoor runit, openrc

@lungdart i also never had any problems with using either (that i didn't cause myself).

but when writing own services, i found that init.d just.... _lacked elegance_ - i feel the more declarative approach of systemd is a better choice compared to the "lol, just chuck a bash script in there" of init.d

that being said, from a dev-perspective, the question is moot. because from a dev-perspective, the "better" system is the one that's in place at the customers location.

@AdamOnAir I was playing with openrc on alpine yesterday and it's simplistic as far as I can tell. I was configuring docker on alpine IN a VM. But when I found out that groups were missing, I thought "ok, that's enough. Now I quit.". But I made a nice init.d service that does nothing