I have the feeling systemd is meant exactly for what you call hobby or novice users.
I actually enjoy some of it on my laptop to be honest ;-)
But in the datacenter it has caused me hours and hours of 'fixing problems that did not exist before systemd came along'.
Most of it's 'improvements' target the desktop user.
Many of it's 'improvements' actually get in the way in the server room.
I mean, why would I want to optimize my boot time on a server with all this parallel startup crap?
The server spends 10 times more time in BIOS and POST then it takes to boot the OS.
It has always been like this. And it still is like this.
From a config management point of view I like systemd. I gives me a consistent API to enable/disable start/stop services. That's awesome. I also like that I can 'override/patch' upstream units without having to maintain a fork. Perfect.
But many other things that came from the systemd ecosystem are questionable.
E.g. systemd-resolved, timesyncd and that kind of stuff.
Maybe these are nice for desktop users who want a click and play experience on their laptop.
No problem with that. But why do they have to break my server's for this?
I mean seriously: Linux on the desktop is irrelevant. Why optimize the whole OS/init for a irrelevant use case?
I have the feeling systemd is meant exactly for what you call hobby or novice users. I actually enjoy some of it on my laptop to be honest ;-)
But in the datacenter it has caused me hours and hours of 'fixing problems that did not exist before systemd came along'.
Most of it's 'improvements' target the desktop user. Many of it's 'improvements' actually get in the way in the server room.
I mean, why would I want to optimize my boot time on a server with all this parallel startup crap? The server spends 10 times more time in BIOS and POST then it takes to boot the OS. It has always been like this. And it still is like this.
From a config management point of view I like systemd. I gives me a consistent API to enable/disable start/stop services. That's awesome. I also like that I can 'override/patch' upstream units without having to maintain a fork. Perfect.
But many other things that came from the systemd ecosystem are questionable. E.g. systemd-resolved, timesyncd and that kind of stuff. Maybe these are nice for desktop users who want a click and play experience on their laptop. No problem with that. But why do they have to break my server's for this?
I mean seriously: Linux on the desktop is irrelevant. Why optimize the whole OS/init for a irrelevant use case?