4 ms·
It's also because Windows after 8ish seem to just assume everyone has an SSD and small file ops are "fast enough" to not care about and sure just throw blocking
by mrguyorama 3y ago
It's also because Windows after 8ish seem to just assume everyone has an SSD and small file ops are "fast enough" to not care about and sure just throw blocking IO into the hot loop nobody cares. NTFS isn't even fast on many small file IOPs but MS don't care, because all their machines have big SSDs and they fired their QA anyway.
What are you going to do, install linux? Then you get to enjoy your package manager deleting your windowing environment when you try to install Steam because of some stupid overlooked thing. You can't even click a single button to roll back your install to a previous known good condition, like Windows has had since like 2000.
- RajT88 3y ago> It's also because Windows after 8ish seem to just assume everyone has an SSD and small file ops are "fast enough" to not care about and sure just throw blocking IO into the hot loop nobody cares. I haven't had this issue, strangely. These days all my OS's are on SSD's though. But that was not the case when I first moved over to Win10 for my gaming PC and work both. The shenanigans with windows updates though... I am convinced that there's something in the OS to intentionally cause strange behavior when updates are pending as a way of incentivizing you to reboot. This didn't used to happen. I haven't yet made the time to properly study it, because it's always at a moment where I have more important things to do.
- ankurdhama 3y ago> You can't even click a single button to roll back your install to a previous known good condition, like Windows has had since like 2000. You can, just use an immutable distro like Fedora Silverblue.