Skip to Content [alt-c]
In reply to Thoughts on the Systemd Root Exploit
Heh... The lock-in is from people that haven't a single damned clue about "mission critical" code from the beginning.
Lennart hasn't done a single project that wasn't troubled, painful, and didn't work so hot until he left it behind. Not PulseAudio, not Avahi, not systemd. He didn't really manage to get it "right" with his very first little project on the design front (You inject as much as 100 msec of latency into sound playback...at the perception level of human hearing...making games difficult to get right...just for starters)- and filled with design features that are...iffy to begin with. Network audio?
Avahi's overengineered but finally useful. Pulse is MOSTLY "good".
But that's in-spite of Lennart. And you're letting this man design and oversee coding that is very much and fundamentally mission critical is job one. They don't care because if it crashes and takes the whole OS with it, we'll just launch a new Container. Yes, this was all done to make containers easier and NOTHING ELSE. There's other ways, other answers to do that, but we're off letting Red Hat lock us in, yet again, into what is good for them and really solely them (ALSA was another example...OSS4, if we'd sorted out the licensing issues was superior and easier to work with, etc. But Red Hat jammed THAT down our throats as well...)
Well, some are working, rather than just bitching, on answers there, myself included.
Reply
Your comment will be public. To contact me privately, email me. Please keep your comment polite, on-topic, and comprehensible. Your comment may be held for moderation before being published.
Your Name: (Optional; will be published)
Your Email Address: (Optional; will not be published)
Your Website: (Optional; will be published)
>
monospaced
Post a Reply
Your comment will be public. To contact me privately, email me. Please keep your comment polite, on-topic, and comprehensible. Your comment may be held for moderation before being published.