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: 0) by Anonymous Coward on Tuesday August 19 2014, @02:34PM
that article is nothing but a simple "muh Unix" rant. parroting the same shit over and over doesn't change the fact that distro developers as well as the silent majority give no fucks about which init system they use, so long as their facebook works. come back with a real argument that has nothing to do with Unix and you get people to listen, until then stop shitting up this site with these autistic ramblings.
(Score: 3, Insightful) by Anonymous Coward on Tuesday August 19 2014, @02:57PM
Fair enough, here are some:
- systemd is supposed to be an init system. It's not.
- systemd is broken by design
- systemd is a trojan horse
- systemd is hard to replace by another init once in place.
- systemd's key developers are obnoxious assholes
your turn.
(Score: 4, Insightful) by tangomargarine on Tuesday August 19 2014, @04:49PM
In the comments above, people explain that systemd doesn't even really accomplish any of the things it claims to do, and manages to shit up the whole place in the process. How much worse can you get?
"Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"