How did you came to that conclusion? In my experience, sysvinit comes with less bloat, and hangs randomly much less than systemd. I've worked with both old debian (sysvinit) and current centos (systemd) systems, and if I had a problem with init, it was always with systemd. If something related to disks or user login sessions fails, with sysvinit most of the time things proceed promptly, while with systemd, you're in for a waitfest/eternal hang.

Systemd seems to be propelled by distro packagers and developers, but for admins/users, it's not that great.