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 mrider on Tuesday August 19 2014, @02:42PM
Just because Netcraft has confirmed it doesn't mean that *BSD is dead. Debian has been my goto distribution for ages. But my next upgrade is going to be to one of the BSDs. The original goal of SystemD was laudable, but the current implementation is execrable.
Doctor: "Do you hear voices?"
Me: "Only when my bluetooth is charged."
(Score: 2) by Pav on Thursday August 21 2014, @12:43AM
Desktop BSD was embraced, extended and near extinguished when Apple grabbed a large portion of their devs. Has this situation changed? I've been in I.T too long to bother with anything except GPL (preferably GPL3 these days). The generation before me picked new/inferior Linux over a mature and superior *BSD in the early 90's for good reason.
After saying that, I still have no idea how to deal with this needless complexity creep. Perhaps some academic needs to come up with a complexity vs functionality metric so we can rank the suckage and name/shame the worst offenders.