It tries to do a lot in a very centralized way and (initially) didn't have many devs so it was kinda risky.
Because it does so much and is centralized, making something that works with it can sometimes be quite the pain. Some init systems just require you to write a script, for example. One little file. systemd requires at least its own special service file and if you want to do anything more complex there are 5-10 subcomponents you might have to study for a while before you can begin.
I think it's a good direction, though. I'd much rather see iterations on this one central system where you can find/edit/start/stop/log services than fight with some random hackneyed init system.
Systemd unit file are not so hard to write really and are much more robust than older script systems, which are usually held together with tape and do not handle failure well. They were always one of the worst design choices of UNIX and are extremely fragile, to order especially. Systemd also keep a central state for services, which is very logical and necessary to manage services to modern standard.
It tries to do a lot in a very centralized way and (initially) didn't have many devs so it was kinda risky.
Because it does so much and is centralized, making something that works with it can sometimes be quite the pain. Some init systems just require you to write a script, for example. One little file. systemd requires at least its own special service file and if you want to do anything more complex there are 5-10 subcomponents you might have to study for a while before you can begin.
I think it's a good direction, though. I'd much rather see iterations on this one central system where you can find/edit/start/stop/log services than fight with some random hackneyed init system.
BROKE: Getting mad at systemd
WOKE: Getting mad at pulseaudio and pipewire.
BESPOKE: Getting mad at macrokernels
2030 will be the year of GNU Hurd on the desktop.
Systemd unit file are not so hard to write really and are much more robust than older script systems, which are usually held together with tape and do not handle failure well. They were always one of the worst design choices of UNIX and are extremely fragile, to order especially. Systemd also keep a central state for services, which is very logical and necessary to manage services to modern standard.
Yeah I've written a few they're not so bad. But it is one of the things people complain about.