That's not how management works. The expenses will be reduced and profit increased by any means, all the time, forever, no matter how much profitable a company already is.
Supposedly it requires additional workarounds to run in safe mode, and doesn't work if the NVMe drive is attached to a RAID controller (whether that's in use or not).
I also wonder whether this feature will be locked to server and the little-known "pro for workstations" variants.
> The native NVMe driver (nvmedisk.sys) replaces the legacy storage path that has routed NVMe commands through a SCSI translation layer since before NVMe SSDs existed.
What? What are Microsoft doing for a decade after NVMe available to consumer grade motherboard?
Seriously, that was my thought too. Even if we were to stretch credibility and suggest that general consumers don't care about this sort of thing, they just released this for Windows Server in the past year?
Windows really is a toy of an OS. It continues to blow my mind that people want to use it as a server OS.
It just seems so beyond-belief that Microsoft keeps having such depraved anti-consumer behavior. Maybe perhaps this was just a not-ready-yet feature folks had enabled being moved around or shuffled. But it seems just as likely Microsoft intends to keep consumers using a decade and a half years old shitty NVMe-downcast-to-SCSI layer indefinitely, to upsell folks to fancier Windows versions or gaming systems. Microsoft intends to keep Windows consumer disk access slow and bad.
As a seasoned Linux veteran & believer, it's somewhat against my interest to share this view, to try to arouse the slumbering behemoth to action. Microsoft not getting the message and doing great misservice to their users is somewhat in my interest. The status quo of Linux being far better at everything is great: gaming is already much faster on Linux, & that should be no surprise, and disk io too. Just holding my tongue and letting Microsoft make a fool for themselves with absymal performance would be ideal. But I also believe in competition, and Linux is going to start slacking off if Microsoft can't be arsed to update a disk io subsystem that was a filthy pitiful hack when they slammed it into service a dozen years ago. We all need some pressure sometimes to get off our hinds, wake the frak up, and pay some attention.
And perhaps, maybe: even Windows users don't deserve this malpractice.
Honestly, who cares if it wasn't ready. It was shipped, available, and required active screwing around by hobbyists to make active. If something goes wrong, thats not on Microsoft - its not an advertised feature. Should have let the hobbyist crowd keep going and kept tabs on performance and crashes.
Its inane that they still rely on scsi downcast, however.
If AI was truly profitable Microsoft wouldn't need to cover their expenses at every other corner.
That's not how management works. The expenses will be reduced and profit increased by any means, all the time, forever, no matter how much profitable a company already is.
Supposedly it requires additional workarounds to run in safe mode, and doesn't work if the NVMe drive is attached to a RAID controller (whether that's in use or not).
I also wonder whether this feature will be locked to server and the little-known "pro for workstations" variants.
> doesn't work if the NVMe drive is attached to a RAID controller
well that makes perfect sense, if its a consumer or prosumer grade raid controller, to be honest.
> The native NVMe driver (nvmedisk.sys) replaces the legacy storage path that has routed NVMe commands through a SCSI translation layer since before NVMe SSDs existed.
What? What are Microsoft doing for a decade after NVMe available to consumer grade motherboard?
Seriously, that was my thought too. Even if we were to stretch credibility and suggest that general consumers don't care about this sort of thing, they just released this for Windows Server in the past year?
Windows really is a toy of an OS. It continues to blow my mind that people want to use it as a server OS.
I am guessing that like ntfs it's a huge legacy spaghetty codebase that nobody understands and thus doesn't want to touch
there is so much to get angry about in the world at the moment.. I'm surprised that this one even registered with me.
They all feel like they're parts of a single expansive pattern.
I mentioned this in the Scott Hanselmen trying to re-allow local-accounts for Windows thread. https://news.ycombinator.com/item?id=47498494
It just seems so beyond-belief that Microsoft keeps having such depraved anti-consumer behavior. Maybe perhaps this was just a not-ready-yet feature folks had enabled being moved around or shuffled. But it seems just as likely Microsoft intends to keep consumers using a decade and a half years old shitty NVMe-downcast-to-SCSI layer indefinitely, to upsell folks to fancier Windows versions or gaming systems. Microsoft intends to keep Windows consumer disk access slow and bad.
As a seasoned Linux veteran & believer, it's somewhat against my interest to share this view, to try to arouse the slumbering behemoth to action. Microsoft not getting the message and doing great misservice to their users is somewhat in my interest. The status quo of Linux being far better at everything is great: gaming is already much faster on Linux, & that should be no surprise, and disk io too. Just holding my tongue and letting Microsoft make a fool for themselves with absymal performance would be ideal. But I also believe in competition, and Linux is going to start slacking off if Microsoft can't be arsed to update a disk io subsystem that was a filthy pitiful hack when they slammed it into service a dozen years ago. We all need some pressure sometimes to get off our hinds, wake the frak up, and pay some attention.
And perhaps, maybe: even Windows users don't deserve this malpractice.
Honestly, who cares if it wasn't ready. It was shipped, available, and required active screwing around by hobbyists to make active. If something goes wrong, thats not on Microsoft - its not an advertised feature. Should have let the hobbyist crowd keep going and kept tabs on performance and crashes.
Its inane that they still rely on scsi downcast, however.
> Should have let the hobbyist crowd keep going and kept tabs on performance and crashes.
Or they believe that it has serious issues in a consumer SKU or consumer application.
Much like oracle MS doesn’t have customers just victims that for whatever reason can’t escape
holy fuck, imagine segregating your customers' block layer
“NVME?? What’s NVME got to do with anything?
It’s the Task Bar!
For goodness sake can’t you see Windows users have lost faith because they can’t move the task bar!”
(Heard in meetings all over Microsoft campus recently).
and then they all break out into song and dance.
If you reaaaly dont liiike it, dun dudun dun!
Lock the taskbar. lock the taskbar! (ref: z0r . de / 2090)