The anti-systemd crowd just seems uneducated to be honest. They still say that systemd is bloated, because they don’t seem to understand systemd is a catalogue of software, not literally everything happening in PID 1.

Moreover none of them really seem to have operated servers at scale to understand why systemd is useful. Your init system is 1000 lines of C? Cool story bro that does literally none of the things sysadmins need to run a server fleet, enjoy gluing everything together with brittle bash scripts.

Pfft. Ever heard of runit or s6(6)?

( https://smarden.org/runit/ https://www.skarnet.org/software/s6/ )

While systemd may be convenient, and more than a simple init & supervision,

it's still slow compared to runit/s6(6).

Let's say I have a larger process-tree.

Let's say I give it's top, or any thread sighup, lazily out of htop.

Systemd? Takes seconds to tear it down, and restart.

Runit? In an instant. s6(6)? Same.

Just a flicker in the corner of my eye.

There is nothing brittle about https://github.com/skarnet/execline which is a dependency of s6.

Tested initially on almost obsolete systems.

First noticed with large firefoxen, with many windows and tabs.

But it isn't limited to that, just any larger process-tree suffices for comparison.

Does still apply to current versions and is reproducible on contemporary systems.

Runit and before it DJB's daemon-tools (and derivatives) have been around for a long time.

S6 came later. All rather good stuff, if one knows them, that they exist at all,

and is able to handle them, which isn't really complicated,

because they never had the history of glued together brittle bash-scripts.

Just saying...….