4 ms·

Overly obvious question, but: Why TF is there nobody on the Windows team who does exactly this type of work? Why are these things even slipping through QA over

Overly obvious question, but: Why TF is there nobody on the Windows team who does exactly this type of work? Why are these things even slipping through QA over and over again? The user-facing layer of Windows is so full of similar problems, yet nothing ever improves, it only ever gets worse.

fassssst 4y ago
Pretty much every engineer on the Windows team does this type of work. When you have 1+ billion computers with an infinite combination of peripherals and environments (what language, what apps are running, etc.), it becomes a game of statistics and prioritization.
- brucedawson 4y ago
  I don't think that is true. If they had that many developers burning down performance issues then bugs like this would (IMHO) be getting fixed earlier. Anecdotally it sounds like a lot of customers are hitting this bug and I'd love to know whether it is known, being investigated, or just noticed now. I'm sure it has been showing up in their start-menu telemetry. I also wonder why they haven't fixed this issue: https://twitter.com/BruceDawson0xB/status/1607163439159611392t https://twitter.com/BruceDawson0xB/status/160716343915961139... And why this was ever allowed to ship: https://randomascii.wordpress.com/2022/09/29/why-modern-software-is-slow-windows-voice-recorder/ https://randomascii.wordpress.com/2022/09/29/why-modern-soft... And why this was ever allowed to ship: https://randomascii.wordpress.com/2022/07/11/slower-memory-zeroing-through-parallelism/ https://randomascii.wordpress.com/2022/07/11/slower-memory-z...
fexecve 4y ago
The Windows team probably has laptops with high-speed SSDs, and tons of RAM, a fast CPU, and a fast internet connection. So now already with that, 13 seconds is probably down to 3 seconds, and they are probably also okay with (sometimes) waiting 3 seconds while the search box opens after pressing the windows key.

fassssst 4y ago

Pretty much every engineer on the Windows team does this type of work. When you have 1+ billion computers with an infinite combination of peripherals and environments (what language, what apps are running, etc.), it becomes a game of statistics and prioritization.

brucedawson 4y ago
I don't think that is true. If they had that many developers burning down performance issues then bugs like this would (IMHO) be getting fixed earlier. Anecdotally it sounds like a lot of customers are hitting this bug and I'd love to know whether it is known, being investigated, or just noticed now. I'm sure it has been showing up in their start-menu telemetry. I also wonder why they haven't fixed this issue: https://twitter.com/BruceDawson0xB/status/1607163439159611392t https://twitter.com/BruceDawson0xB/status/160716343915961139... And why this was ever allowed to ship: https://randomascii.wordpress.com/2022/09/29/why-modern-software-is-slow-windows-voice-recorder/ https://randomascii.wordpress.com/2022/09/29/why-modern-soft... And why this was ever allowed to ship: https://randomascii.wordpress.com/2022/07/11/slower-memory-zeroing-through-parallelism/ https://randomascii.wordpress.com/2022/07/11/slower-memory-z...

fexecve 4y ago

The Windows team probably has laptops with high-speed SSDs, and tons of RAM, a fast CPU, and a fast internet connection. So now already with that, 13 seconds is probably down to 3 seconds, and they are probably also okay with (sometimes) waiting 3 seconds while the search box opens after pressing the windows key.