Two things can be equally true. Systemd rocks and sucks major balls at the same time.
Systemd is a great init system when it comes to laptops and desktops that need to dynamically change based upon external events. Like closing the the lid on a laptop or plugging a device into a USB port. In that regards, it's a lot like launchd on a MacOS.
Where systemd sucks is in server applications where you want simplified, stable, secure, maintainable specialized use systems that should change and reboot infrequently.
It is for this reason, I have stayed with older Linux Distros and returned to *BSD for many of my server installations. All the while, I hope the distros learn the philosophy of UNIX and come to their senses.
Slashdot Mirror
Two things can be equally true. Systemd rocks and sucks major balls at the same time. Systemd is a great init system when it comes to laptops and desktops that need to dynamically change based upon external events. Like closing the the lid on a laptop or plugging a device into a USB port. In that regards, it's a lot like launchd on a MacOS. Where systemd sucks is in server applications where you want simplified, stable, secure, maintainable specialized use systems that should change and reboot infrequently. It is for this reason, I have stayed with older Linux Distros and returned to *BSD for many of my server installations. All the while, I hope the distros learn the philosophy of UNIX and come to their senses.