Comment by notjustanymike

1 day ago

> It's unclear why January's security update for Windows 11 has been so disastrous. Whatever the reason, Microsoft needs to step back and reevaluate how it developers Windows, as the current quality bar might be at the lowest it's ever been.

I think I might know...

17 comments

notjustanymike

Reply
rootnod3  1 day ago

Vibe coding to the max. Forcing employees to use it and that’s the large scale result. Cause it’s garbage. Hands down on large scale it just doesn’t work. Especially on something the scale of an operating system.

There will be the usual downvotes and I’ll take em. If the pro-AI folks can’t convince me that LLMs are able to write and maintain systems at that scale, that will be par for the course.

Wait, “you just didn’t write enough spec and unit tests for the LLM to do it correctly and you are promoting it wrong”.

game_the0ry  1 day ago

> I think I might know...

I will say it for you -- they're moving too fast with AI.

  • Topfi  1 day ago

    I wish this were a recent development, connected to major improperly reviewed code changes provided by LLMs, but let us be honest, MSFT has had an appalling, frankly embarrassing track record in this regard dating back literally a decade plus now.

    I've experienced it more than once on my Surface back in the day [0], the entire globe was affected by Crowdstrike which also was caused by a lack of testing on MSFTs part and there are numerous other examples of crashes, boot loops and BSODs caused by changes they made throughout the years [1].

    Frankly, simply, no matter whether the code changes are provided by the worst LLM or the most skilled human experts, it appears their review process has been faulty for a long time. Bad code making it into updates is not the fault of any new tools, nor (in the past) of unqualified developers since, frankly and simply, the review process should have caught all of these.

    Mac OS can be buggy and occasionally is a bit annoying in my case (Tahoe though is actually rather stable besides a few visual glitches for me, surprising considering a lot of my peers are having more issues with it over 25) but I have yet to see it fail to boot solely due to an update.

    Linux distros like Silverblue have never been broken due to an update in my experience (though there are famous examples like what happened a while back with PopOS). With immutable distros like Silverblue, even if you intentionally brick the install (or an update does break it), you just select the OSTree prior to the change and resolve any issue instantly.

    For an OS one is supposed to pay for both with money and by looking at ads, Windows has been in an inexcusable state long before LLMs were a thing. Considering such major, obvious issues as "system doesn't start anymore" have been falling through code review for over a decade now, imagine what else has fallen through the cracks...

    [0] https://www.computerworld.com/article/1649940/microsoft-reca...

    [1] https://support.microsoft.com/en-us/topic/you-receive-an-eve... and https://www.eweek.com/security/microsoft-yanks-windows-updat... and https://www.404techsupport.com/2015/03/12/kb3033929-may-caus... and https://learn.microsoft.com/en-us/troubleshoot/windows-clien...