Unfortunately, for my needs, simplicity and understandability are far more important than a fast boot and feature-rich management of the runtime environment. I need to KNOW that things are being handled properly and securely. That's become far more important since Snowden showed us, not that the spooks were getting into our computers (which we'd already figured was happening), but how DEEPLY and EFFECTIVELY their technology and personnel are able to do so.
So systemd is good news for you, as it removes the frightening security mess that shell initscripts were by configuration files that are not executables.
Trojan could be hidden anywhere with sysvinit, especially with links everywhere, it was just impossible to monitor. Security is one of the reason I stopped using sysvinit more than a decade ago on my servers and desktops.
I need to KNOW that things are being handled properly and securely. That's become far more important since Snowden showed us, not that the spooks were getting into our computers (which we'd already figured was happening), but how DEEPLY and EFFECTIVELY their technology and personnel are able to do so.
It always was important, Snowden just opened more eyes, but lots of people already knew, some still have their eyes closed though.
If the improved functionality is at the cost of burying the configuration and logging in non-human-readable form and entangling diverse processes into an interlocking mass under a complex and ever growing manager, the shark has been jumped.
That was the sysvinit situation, even one of the big problem of initscripts, fortunately systemd corrects this. Now all the truely active configuration is easily readable as is logging, which is readily available, not scattered across 3 or 4 different files.
Though Linux has been becoming (MUCH!) more usable with time, its configuration has been buried progressively more deeply under more and more "convenient and simplifying", but non-transparent, configuration management tools. Systemd is the continuation of the trend. But it is also a quantum leap, rather than another thin slice off the salami. So it has apparently created the "Shelling Point", where a lot of frogs simultaneously figure out that NOW is the time to jump out of the pot.
So that is the nonsense that is going through the head of non-technical people unable to understand technical concepts. It looks like insane thoughts for something like systemd that is actually very simple to explain what it does to non-technical people, but not so simple to code.
You'd better not use buzzword you hear in movies, they don't understand that they're saying nonsense either. For example "non-transparent, configuration management tools", this doesn't make any sense. systemd is not even on the same level as these, it's part of the core of the OS.
It's been a great ride. It had the potential to be even greater. But I think this is where it took the wrong turn and it's time for me to get serious about switching.
There's good reason to switch to NetBSD at work, on the product. (The code supporting the secret sauce is on the user side of the API and is Posix compatible, so it should be no big problem.) Porting my laptop, home servers, and desktops to OpenBSD now looks like it's worth the effort - and less effort than trying to learn, and keep abreast of, the internals of systemd.
systemd detractors don't make any sense : switching to another completely different kernel and OS is somehow easier than learning a new init system commands.
I don't remember people saying such nonsense when Red Hat appeared with chkconfig or service, or when Ubuntu launched Upstart. And I can guarantee it's easier to learn a new init system than switching OS. Also, I don't understand why someone would advertise that he gave up because of his inability to grasp new technology and instead took the harder route because he doesn't understand what he's doing. It seems like sometimes everyone who switches to a BSD feels the need to advertise it.
Call me if somebody comes up with a way to obtain the key benefits of systemd in a simple and transparent manner, rather than creating an opaque mass reminiscent of Tron's Master Control Program. (Unfortunately, the downsides of systemd's approach seem to be built into its fundamental structure, so I don't expect it to evolve into something suitable, even if it's forked.)
Nobody will call you, you made your choice, try to live without being babysitted. Actually, people have obtained the key benefits of systemd for years by just adopting it, giving bug reports and helping improve it. A very simple and transparent manner to do it is to get it on a new and fresh system.
People who have problems with systemd are people that are migrating systems to it, which requires you know your systems well, and how a Linux OS works, from the plumbing and up.