Sorry, I made a typo, I meant drives, not drivers.
Firmware is software embedded in the SSDs, and Windows has no control over them. Microsoft can’t fix this and the SSD manufacturers here are at fault.
Do note that I escaped Windows in 2017, and wouldn’t like to go back to it because of how nauseatingly user-hostile it is.
Eh… Reading the article it’s clear what’s causing this are faulty SSD drives. Windows might stress their crappy firmware, but the fault lies on the hardware.
So another benchmark dressed up as a game?
EU law makes it a requirement to provide updates since a company stops selling the device. So they better fix it or they will be sued.
https://energy-efficient-products.ec.europa.eu/product-list/smartphones-and-tablets_en
Isn’t that the bare minimum mandated by the EU?
We did notice, on Sunday, along the techsphere ibterestef in handheld consoles / PCs. What took so long to write this informercial piece?
The feeling after reading this is that the automotive missed on software’s best practice’s from at least the last 2 decades. Maybe it’s because I’ve heard people saying they refuse to buy cars made after 2010, because of the bad quality
It didn’t get review-bombed. It got negative reviews after the last update because people don’t like it.
Personally I bought it and don’t like it: it’s an awkward mix between diablo-likes and souls-like, while not reaching the heights of either, it also has its own unresolved issues, like lack of descriptions for weapons or abilities. This might have been fine on the first release of the early access, but we’re almost a year in and people expect initial 8ssues to be fixed.
Did Synology just hire some brain dead Broadcom executive?
Well, Citrix’s CEO was Broadcom’ software boss
And also hasa place at the US treasury, he’s DOGE-affiliated as well: https://www.crn.com/news/cloud/2025/citrix-parent-ceo-krause-on-doge-role-we-re-applying-public-company-standards-to-the-federal-government
Xcp-ng might have the edge against bare metal because Windows uses virtualization by default uses Virtualization-Based Security (VBS). Under xcp-ng it can’t use that since nested virtualization can’t be enabled.
Disclaimer: I’m a maintainer of the control plane used by xcp-ng
But the individual network packets are usually at most 1500 byes long, and applications encrypt the content. Hashing doesn’t prevent jack squat. It’s more likely to be DNS + IP blocks
Sounds like my next phone won’t use Android then, and I’ll tell everybody to avoid it. If only Linux mobile was in a hood place :(