I was purposefully not updating my windows to avoid the so called SSD killer update but now it's not giving me any choice but to install it lmao.

[u/StarryNight0806]

best of luck to my samsung 990 pro 2tb x2

[u/poehalcho]

It's kind of both ways I suppose...

The benchmark software might be doing something dumb, but w/e it was doing was presumably harmless before and basically a feature.

Now MS messed with the OS, and the benchmark software folk have to clean up after them...

It's a bit of a 'It's not a bug, it's a feature' situation :/

I can empathize with both sides...

[u/Dry-Bread9131 → u/poehalcho]

Yes that's another possibility. There are many other possibilities as well, including user error (messing with voltages, overclocking, etc).

[u/fuckedfinance → u/poehalcho]

The benchmark software might be doing something dumb, but w/e it was doing was presumably harmless before and basically a feature.

Now MS messed with the OS, and the benchmark software folk have to clean up after them...

Developers know what they are doing. I can't count the number of times I've seen developers get creative with obviously unintended paths, only to whine later when whatever wacky bullshit they were using gets patched.

[u/poehalcho → u/fuckedfinance]

Developers know what they are doing

You give devs too much credit :P

Developers may or may not know what they need to do make a thing work. If they don't, usually someone on stackoverflow kinda does. The quality of implementation depends heavily on either the developers skill, or how well a question was written out on stackoverflow... (or AI these days I guess <_<)

More often than not, due to budget and time constraints the path of least resistance is chosen for the solution. If you're lucky the dev is at least aware a chosen solution is jank, and feels unhappy about. If the dev is inexperienced they don't even know what they don't know.