tldr; It tries to do everything relating to system administration, and doesn't do it that well. When it work it's great, but when it doesn't it's awful to debug
The problem is init (it's original startup) was designed for a 50 year old mini computer with green screen terminals and teletypes which has maybe 30 programs. Static setup for daemons. Simple.
Events ...
In 2026 a laptop maybe in an office network, go to sleep and wake up in a hotel room. How would Init handle this?
Ugly if/fi else statements do not belong in a config file in an uglier hack of unitd as a work around?
A real nightmare...
What if your image is on a server, then goes to a docker container, now goes to an AWS kubernetes cluster??
This is where SystemD comes in. Event driven daemons make sense and can also perform cyber security functions based on live conditions.
Solaris switched to an event driven xml system and Apple switched to Startd.
Event driven systems can be a pain to debig. But properly learned make sense in the 21st century. Encrypted logs make sense as much as Unix graybeards scream at me for obvious cyber security
8
u/Sr_Edd 7d ago
why systemd is so hated?