4 ms·
If your software can break your hardware on a normal PC (not talking industrial robots or something), your hardware is flawed.
by BenjiWiebe 1y ago
If your software can break your hardware on a normal PC (not talking industrial robots or something), your hardware is flawed.
- wiseowise 1y agoYour finger can also be easily cut off by a wood cutter, doesn't mean that it has to be.
- gchamonlive 1y agoWhile 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.
- ghosty141 1y agoWhat? 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…
- gchamonlive 1y agoIs that the case in the article? Why did it happen after the latest update? Why did it need a patch then? Your comment seems out of context.
- gruez 1y agoNo, 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.
- gchamonlive 1y agoSo care to answer? "Is that the case in the article? Why did it happen after the latest update? Why did it need a patch then?"
- gruez 1y agoI replied to your other comment asking the same question 10 minutes ago.
- hulitu 1y ago> If your SSD is old and close to failure, you can’t blame the software pushing it over the edge. If you have an old car, you shouldn't press the gas pedal. /s
- nottorp 1y agoNot 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?
- gchamonlive 1y agoSeems to me like either technical debt or symptoms of data farming, where the OS hoards data from the system for later analysis
- c-hendricks 1y agoOne part of one component of the task bar is written in React but go off
- gchamonlive 1y agoThe 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.
- c-hendricks 1y agoThen your prayers have been answered, the single component that uses React in the Windows taskbar doesn't use a web browser.
- deleted 1y ago[deleted]
- bboygravity 1y agoThere's also not really an alternative to Windows on PCs. Linux still has tons of driver issues and is a massive time vampire with its "type magic spells into a terminal for hours to get something done" GUI. Mac is way more expensive and doesn't run a ton of apps available on Windows.
- hulitu 1y ago> There's also not really an alternative to Windows on PCs. cough Linux, BSDs, Solaris clones cough
- Ukv 1y ago> 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.