Maybe they should roll X, the desktop environment, and hell, why not imagmagick and gimp into Systemd already?
Systemd sucks for the enterprise, and there wasn't anything really wrong with SysVinit. Yes, init was antiquated but it fucking worked and it is stupid-easy to navigate and troubleshoot very, very quickly - and very easy to extend init scripts with additional commands. You simply can't do it with systemd.
Whatever happened to the UNIX mantra of a single tool performing a single task, and perform that one task extremely well? Systemd does far too much, and not any one task particularly well. "runlevels" are overly complex to configure, it totally fucks up syslog and boot logging (logging to binary files? Really? Dafuq?), and a true single user mode is now history, requiring you to boot to an alternate directory or from a boot disk if you need emergency access. Oh, and it fucks up networking by changing NIC names. What the hell was wrong with eth0 and eth1 anyhow? I know the MAC address of a given interface. I don't want names generated by "location on the board;" I want eth(n).
It sucks that RHEL has jumped on the SystemD bandwagon along with everyone else. I think RedHat have lost their minds; I think a PHB saw SystemD and said "oooh, shiny" and saw that Ubuntu and OpenSuSE were riding the bandwagon. The thing is, I'm okay with it on the desktop; if a desktop crashes no big deal, but if a server breaks it will be far more time consuming to recover if a given tape is not available and we need to wait on Iron Mountain.
I hope whoever made the decision to go with SystemD at RedHat dies in a fire. Seriously. SystemD takes on far too much, and goes against everything *nix is supposed to be about.
One tool should perform a single task and perform that one task perfectly.