5 ms·
Whenever I have to start windows 10, I still see the same kind of bugs, that were present on XP. One example: They seem to be simply unable to fix the icons "ne
by zelphirkalt 4y ago
Whenever I have to start windows 10, I still see the same kind of bugs, that were present on XP. One example: They seem to be simply unable to fix the icons "near the clock", which are still shown, when some app has been killed, until you hover over them. Things like that, but of course also lots of stuff that affects people more in form of annoyances, making every action take at least twice as long as on GNU/Linux distros I run. It only takes minutes, and I am already frustrated with the system, because everything takes so long to do.
- s0l1dsnak3123 4y agoOne similarly ignored bug that springs to mind is the performance of the "Send To" context menu item in File Explorer. I always dreaded dragging my mouse over it by accident.
- notriddle 4y agoThat is a design flaw that cannot be fixed without breaking the API: https://devblogs.microsoft.com/oldnewthing/20190528-00/?p=102522 https://devblogs.microsoft.com/oldnewthing/20190528-00/?p=10... I'm pretty sure there are a lot of those.
- warkdarrior 4y agoApparently nobody at Microsoft thought about the Windows registry as a database, which of course needs indexing to be performant.
- account42 4y agoThey could also cache that computed menu and proactively update the cache whenever the relevant keys are changed. Either way, pretty far from "cannot be fixed without breaking the API".