This. I for one don't miss the mess of shell scripts for network management, init, bootloader, cron, etc. I personally think systemd already does 10x better at each of these tasks then the broken scripts have ever done.
This. I for one don't miss the mess of shell scripts for network management, init, bootloader, cron, etc. I personally think systemd already does 10x better at each of these tasks then the broken scripts have ever done.
That's not what has been done.
systemd unit files are not "scripts". They are declarative configuration files, usually orders of magnitude smaller than the initscripts, network scripts, etc. that they replace. The Apache unit file on RHEL7 is ~17 lines long, and it replaced an initscript that was a couple hundred lines long.
It is a difference of both degree and kind.
Just saying, the de facto ways of using systemd are starting to diverge a lot from the intended behaviour. And of course, the de facto usage is what we'll judge each piece of software's merits on...eventually.
On the other hand, Linux has a history of _forcing_ desktop users to mess with device management for the simplest of tasks, e.g. making their audio devices work.
So you've never restarted a service on your desktop system?
I don't use a Linux desktop (I often retry) because that is unattainable.