openrc

Switching to OpenRC would probably have fixed that aspect, but systemd solves many more problems that distributors faced and OpenRC did not address, faring more positively in a costs/benefits analysis.

Why would you punish yourself with various *BSDs when you can have OpenRC and more advanced ports on Gentoo?

Gentoo by default prefers OpenRC over systemd, though you can chose which one you want while installing.

If you want just a service framework without init, then you can look at OpenRC, too.

Upstart jobs are really simple, and OpenRC and modern BSD initscripts are also much simpler than SysV (and old BSD) initscripts.

I knew sysv/openrc/bsdinit and I liked them so for the first month or two I utterly despised systemd.

For example, the only alternatives that have been debated primarily were Upstart and OpenRC.

About a year ago, we started switching over new servers to systemd instead of openrc at work.

At the moment I'm using OpenRC which does exactly that on top of sysvinit, as are most Gentoo users.

Use OpenRC on Gentoo and keep on enjoying Linux.

I really wish Debian would have gone with OpenRC for that reason.

At least that's what OpenRC has been doing.

If it was "just a init", it would be just as replaceable as sysv, openrc or runit.

I actually ripped it out on my old work computer and replaced it with OpenRC (to fulfil my goal of "something Gentoo-like but without all the compiling"), but on this machine I decided I'd keep systemd around for at least a few weeks because I wanted to get out of my comfort zone and learn something new.

I've discovered there's a bunch of stuff to really like about systemd (in particular, "systemctl status" is amazing ), but on the other hand, I really miss OpenRC, and I happen to prefer its idioms over systemd's (I'm sorry, but you will never convince me that INI-style syntax isn't the ugliest thing ever).