Re: Systemd - the Init of the Beast
This is an unfortunate truth.
There are good ideas in that there systemd, but there are also a LOT of very bad ideas.
I guess trying to solve the messy traditional insecure, non-transactional-state, convention-based alignment of scripts and making possible "fast boots" on devices that are switched on and off often is worth it... but...
It has the smell of a Windows solution. Like the "Registry"
The first problem: WHY SO COMPLEX
The second problem: WHY SO BINARY
The third problem: WHY SO OPAQUE
Trying to understand what went wrong and why something isn't working feels like being at the end of a labyrinth, or at the end of having made an error in a git repository.
What happened to the Art of Unix Programming?
I have been sitting through a few days of my holiday trying to "get" systemd, to no avail.
Maybe it's me.
Maybe it's systemd.
It is too complex.
I want to deny it.
It is impossible to deny.
Maybe systemd v2 will be viable.
What is there now isn't.
Biting the hand that feeds IT
