Conversation
Notices
-
!selfhost !selfhosting Remember to bow down before our great god Lennart Poettering: https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet
- Claes Wallin (韋嘉誠) and ghostDancer like this.
- ghostDancer and Claes Wallin (韋嘉誠) repeated this.
-
@benfell it's a bug in software. What's the fuss ? They've existed before and will again.
-
@kat the fuss arises because this is an overly complex and crappily-written init. Job 1 needs to be robust. Systemd can never be robust because it's far too complicated. Nearly as important, Lennart Poettering has about the worst case of narcissism anyone has ever seen in a programmer: Nothing is good enough unless he's rewritten it or piled on layers of bloat atop it. It's extremely troubling that Linux distributions are enabling someone who needs to be taken far, far away from a keyboard and gotten psychiatric help.
-
@benfell I'm not competent to assess an init job code, or peoples mental health.
-
@kat None of us can be competent in all things. That's why there are many of us, so we can each have our own set of talents.
But while we might expect it in a pubescent male, there is clearly something deeply wrong, mentally, with any adult who insists that everything must be done *his* way. One doesn't need a credential to understand this most obvious point.
As for code quality, I rely on others who are programmers qualified to evaluate code quality. And understanding the importance of job 1 on any UNIX or UNIX-like system entails certain obvious conclusions, hence that whatever you have for init must be robust.
I understand lots of people didn't like init scripts. Hell, I don't like init scripts. But it's really, really hard to see how that required writing a whole new init with the worst case of mission creep in programming history, taking on ever more functions.
There are no great mysteries here. And many, many people have raised these objections over a period of many years.
David Benfell
kat
All Chirp! content and data are available under the