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: 3, Insightful) by tangomargarine on Tuesday August 19 2014, @04:43PM
Like trying to change the tires on a moving vehicle?
"Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
(Score: 2) by kaszz on Tuesday August 19 2014, @08:20PM
Well the first order of the day is to stop the octopussy from growing (seems Linus has done some moves towards this). Next either many small steps is taken to fix this or one stop the "vehicle" and do the big axing. Linux kernel seems to have these big change events now and then anyway.