What’s wrong with systemd? Lots! Frankly the design is appallingly bad.
To quote from a recent post on Slashdot post:
It abstracts services to the point you can’t find them.
It breaks existing sysv startup/shutdown scripts for commercial software. (The reply from vendors of commercial software is pretty unison: We don’t support systems with systemd)
It assumes start and stop are always oneliners, so you end up writing startup/shutdown scripts anyhow cause systemd isn’t good enough.
It breaks standard runlevels.
It uses the old MSDOS .ini file format, which is severely sysadmin-unfriendly (grep doesn’t understand MSDOS [section]s, for example). … and quite a lot more.
In short, it was clearly written by someone who didn’t come from a Unix background. … or, just try “systemctl -a | cat”[*] , and compare that to “chkconfig” and “rc-update show”.
The fact that systend was approved for inclusion in Fedora before it was even half baked shows how broken the Fedora development process has now become.