Comment by jauntywundrkind
3 months ago
This is an thesis without argumentation. You've made no assertions and no statements that can be validated or refuted. You've said nothing. Few systemd haters do, in my view.
There's a lot of reasons to be pro systemd, because it does so much cohesively & well.
But if we just look at the task of running jobs, if we ignore all the other excellent management & other things in the systemd monorepo: when it comes to running programs, systemd is millions of miles head and shoulders above everything else. Like, everyone else was throwing shit up in the air, and systemd was launching fucking rockets. Nothing else has had even the faintest dose of taking itself seriously or trying to get good: it's all been sad recreations of 1970/1980's with no acceptance that the scope needed to be bigger, that we should have better more secure ways of running services.
Upstart may have been a semi ok way of wiring some kind of graph of services together, in an event based way. But honestly I prefer systemd's level-based way, rather than evented, because events don't reconcile in stable ways and level-based relationships do, are understandable not just sequences of actions but as relations of systems.
Its daunting as fuck, and I think this is why most haters hate systemd: because they don't want to get better. But a third of what's available in systemd.exec and systemd.service is absolutely crucial brilliant bundled-in ways to make your service more secure, to make it less of a risk. It exposes incredible awesome things the OS could do that most people simply never got good at doing, that the anti-pattern of sysv never could encompass. SysV said it was up to every service to define their own init scripts, and most of these were very very very dumb init scripts, bespoke and unique and brutally dumb mostly, grafting some random shitty bad shell scripting to running something in the background. Systemd exposes a cornocopia of offerings that Linux has to do this, but securely, safely, with isolation, in a standard, clear/concise (not having to delve into bespoke shell scripts) cross-cutting/repeatable way. Whats on tap here is amazing. None of the haters seem to have the faintest most remote appreciation or interest in getting good, in making any of this incredibly good potentiating shit available or on tap, much less in any repeatable consistent clear fashion. I think the haters are playing at such deeply sad forsaken stupid levels, actively fighting the ability to appreciate even remotely the awesome forces they - if they had any idea what was good for them - would be moving towards, be it via systemd or other.
Yes, 1/3rd of this is incredibly niche. 1/3rd is common/good/necessary and somewhat buried amid the rest. 1/3rd of it is just fantastically good security/safety practice that no one did, that no one knew about, that's just on tap, and easy to bring in, that's so accessible, that was so hard & weird & difficult to do before, that's such a colossal improvement in posture:
https://www.freedesktop.org/software/systemd/man/latest/syst... https://www.freedesktop.org/software/systemd/man/latest/syst...
> ...everyone else was throwing shit up in the air,
Yah, well, systemd has thrown shit at me. Depending on the Distro, time, maybe hardware/firmware too, while other inits&(service-)supervisors didn't at the time.
> ...and systemd was launching fucking rockets.
Which sometimes go BOOM in spectacular fireworks. It's not exactly that it has reached the state of full reusability like SpaceX intends to ;->
> ...because they don't want to get better.
Maybe some, not me.
See? https://postimg.cc/CZtH4rHp Système D whoohoohoondrrbarr! Arr tyarr tyarr!1!!