We've been explaining this for years, only to face the slurs and word-game attacks by the systemd advocates.
Once more unto the breach, dear friends
First, re: monolithic. What IS a factual effor is that, when discuss software, the term "monolithic" has anything at alkl to do with the number of files a project happens tro compile into. To claim that something has a "monolithic design" is to claim that the features are far too thightly coupled, and cannot be replaces individually should the need arise. That need can range form personal opinion, to some horribl security flaw being discovered. Really, this is an extension of the idea of trying to write "modular code" instead of an unmaintainable pile of spaghetti. Systemd is the worse case I've ever seen a project heading down the "spaghetti" route, and maintainabiliity in the future is goign to be painful once the needs of the real world start making demands against the "simple" desing systemd started as. In this sense, it is a repeat of the "hal" fiasco. Only worse., given how much more money and time that has been invested so far.
That's just a general technical critique. The real problem with systemd is not technical, but the fact that it is actively trying to remove the unix nature of linux and replace it with a more windows-ish style. Yes, that is opinion.. Some of us are of the opinion that we came to unix to get a better OS than the hard-to-use, obscure-by-design windows style of OS. So we will never be using systemd, as the very nature of what systemd enforces goes against the very reason we currently chose to use linux in the first place. The only reaon you see anger here is because Lennart choose the wrong way to implement these goals. He could have forked off a ux and made his own sandbox where he is free to do whatever he wants. Instead, he is ripping apart a place others call their home.
There is an evern deeper problem in play here, too. The maintainability is enough of a reason for the sysadmins to fear systemd, and my personal opinion and personal requirements are enough for me to avoido systemd, but those are both local concerns. The bigger problem, which rarely talked about due to the systemd advocates yelling about everything else and idstracting a lot of people with technical minutea is a problem of ideology and Free Software.. As we used to say here on /. many years ago, sometimes the "free as in speech" of Free Softwware is more important than the "free as in beer" ($$$/cost) of Open Soruce. See the the usual sources like the FSF foir why; what matters is some of us choose to release projects under the GPL, for ideological reasons, and not the "Lesser" variant, the "LGPL". This makes it harder to use tsome software in proprietary code., which was the intent behind the choice of the GPL over the LGPL.
Well, that pisses off a lot of people, would would liek to sue Free Softwarein their products (distribution), but not be bound to the GPl's requirements. Which brings us to how systemd is an end-run around the GPL in a new variant on "tivoization". (k)Dbus is simply an excuse to say you're not "linking" to GPL code, by making all API calls into RPC. As someone who has worked on building a community of Free Software, this will be a devistating setback. (stevel explains it in more detail at that link)
Of course, the fact that systemdj's compartmentalization (with cgroups) to create a purposfully opaque box you're not supposed to care about is exactly how you would pull some scheme to force DRM into linux, and I'mm sur ethe NSA just loves having such a huge pile of new, overly complicated, pile of C code placed into such a key position. These are good reasons for avoidin systemd, but like the technical arguments , are not partciularly important.
//Just watch: I"ll be accused of being "supid" or "paranoid" for posting this, yet nobody will refute the main point about how you firce the GP/LGPL distinction to vanish when tall API *mist* be done through (k)dbus. I wonder if JTRIG is paying any of them?