Care to elaborate?
Systemd has a few nice features that I (as a systems admin of thousands of servers) really like such as:
- simple "init script" like upstart, so magical or crappy shell scripts from vendors are a thing of the past. A standardized unit file
- Ulimit support natively as part of the format
- Limiting via memory/disk/cpu cgroups to contain buggy apps (hello mysql!)
- Process restarting so tools like supervisord, monit, runit, etc are no longer necessary
- It can _always_ stop an errant daemon as it uses control groups to do so, sysv init was sometimes buggy in this regard
- Private /tmp (via filesystem namespaces), limiting system calls a service can run, tcp wrappers, read only parts of the filesystem (like /etc) are all trivial to add to any legacy service such as bind or sendmail and a supported part of the systemd unit file definition.
RHEL/CentOS 7 also include some super nice things like the new abrtd for centrally reporting any application coredump/kernel issue, pacemaker/crm for high availability clusters, and just a lot newer linux userspace. (yay for du -hsc | sort -h | tail)
As an _actual_ user who uses RHEL/Debian/etc on bare metal at scale, I really see nothing but awesome in RHEL7. It is just like I see awesome in Fedora 20 or in the latest Ubuntu/Debian. The Linux ecosystem has massively grown. Now we have a serious engineering company putting a lot of resources into supporting a new operating system. I'd love to see some of the technical reasons you have the opinion you do.