While this is largely true, that's no excuse for a system such as Windows to brick SSDs like that. It's still by far the most popular operating system despite Microsoft's best efforts into enshitifying it.
Windows is therefore going to be used by a wide variety of systems, including those with low grade hardware parts. So it either has to be part of windows quality control to test these low end systems or it should make it very clear about the system requirements.
Either way, the problem was patched, which makes it a problem on windows side.
> that's no excuse for a system such as Windows to brick SSDs like that [...] it either has to be part of windows quality control to test these low end systems or it should make it very clear about the system requirements
If this was a widespread problem I'd agree it should've been caught during testing and mitigated, but it doesn't sound like that's the case ("We looked around and could not find other reports resembling such situations"). As far as I'm aware it's just one Twitter thread reporting this, not all/many low end systems. Only so much Windows can do if it's just a faulty batch of SSDs, or even an incorrectly installed part in the user's setup.
> Either way, the problem was patched, which makes it a problem on windows side.
Has it been? I can't see Microsoft even verifying that the issue exists yet.
Not to mention that I don't see why Windows Defender should generate such heavy write workloads... an antivirus has no reason to. Have they rewriten it in React like the crippled taskbar?
The acceptable amount of browser in the taskbar should be zero. Teams widget also gobbled memory just because it spawned an Edge worker, even if you didn't open or logged into teams. You start to make these concessions, no wonder windows is a bloated mess these days.
What? If your SSD is old and close to failure, you can’t blame the software pushing it over the edge. If a company sells parts that can’t handle writes that are within spec then I’m sorry you bought junk…
No, your comment is out of context. If you read the comments in this thread, it's clear that the this subthread is presupposing the issue caused by bad hardware, and debating what obligation (if any) microsoft has.
