4 ms·
Goodness the start bar on Windows. For something that is meant to be a key part of both the mouse and the keyboard workflow, how can it be so slow? My work co
by dm319 5y ago
Goodness the start bar on Windows. For something that is meant to be a key part of both the mouse and the keyboard workflow, how can it be so slow? My work computers can hang for so long on it, that it is quicker to find the application shortcut on the desktop.
- hulitu 5y agoMaybe because telemetry :).
- donatzsky 5y agoI believe it's not really an integrated part of the Explorer shell anymore, but rather a separate process that gets launched every time you open the start menu.
- coffeeking 5y agoYes, there are separate processes, however a new instance is not started each time you open it - the same window is re-shown. Taskbar: explorer.exe Start menu: StartMenuExperienceHost.exe Searching: SearchApp.exe So, when you hit a key with the start menu focused, it closes the start menu and opens the search window (with the search text initialised with that key). Perhaps keystrokes are lost during the switch.
- dspillett 5y ago> how can it be so slow? Because it is trying to be all things to all people: including supporting sponsored content and integrating with any fancy new/copied idea that the company is pushing (which may be quietly deprecated in the next major revision, but the hooks left adding abstraction load to everything else so that the few who actually found it useful don't complain).
- totalkrill 5y agoJust you wait until they want to be able to run apps inside of it. Because they probably will want to do that. Unfortunately
- dspillett 5y agoThey've sort of already tried that, with animated smart tiles that were used by apps on Windows Phone and Win8. Not something I've seen recently, not sure if that is due to it being deprecated of if people just aren't using it on desktop as the menu is never visible for any considerable length of time.
- AnIdiotOnTheNet 5y agoComputers are ludicrously fast nowadays. Games are capable of doing a whole lot of shit in <16ms consistently while responding to user input, so I don't buy this "it's doing a lot!" argument, it is coded badly.