The good people over at Infoworld have published a story outlining why they feel systemd is a disaster.
Excerpt from Infoworld:
While systemd has succeeded in its original goals, it's not stopping there. systemd is becoming the Svchost of Linux—which I don't think most Linux folks want. You see, systemd is growing, like wildfire, well outside the bounds of enhancing the Linux boot experience. systemd wants to control most, if not all, of the fundamental functional aspects of a Linux system—from authentication to mounting shares to network configuration to syslog to cron. It wants to do so as essentially a monolithic entity that obscures what's happening behind the scenes.
(Score: 2) by morgauxo on Tuesday August 19 2014, @04:09PM
Nope, still don't get it.
What are you setting up? Most modern end-user oriented distros autodetect everything! It just works!
Or, if it doesn't it almost always means you have unsuported hardware. Systemd can't fix that!
What is Systemd replacing that a 'normal' computer user would EVER have touched or even seen?
If you are spending hours configuring openrc or some other startup scripts you must be doing something that this new target audience will not be interested in anyway!