

It isn’t the details or severity of the break that matters.
It’s that the quality control process is SUPPOSED to catch that, and whatever sorry excuse for a process they’re using now ALLOWED a break that was obvious, visible, and repeatable, inside a critical, core function of the operating system, to make it to the end users, something that should trigger as an immediate, flashing warning light. That means the entire quality control process at the very least is SEVERELY compromised and unreliable, and there could very easily be MUCH more severe vulnerabilities and bugs hiding underneath that AREN’T immediately visible. To anyone who has done any professional development for non-disposable code bases, this isn’t a whisper of a problem - it’s an air horn.






Linux doesn’t charge hundreds of dollars per license to fund the development, rake in billions in profit, and then funnel that money into stock dividends instead of a proper quality assurance team.