[thworp]

It's not just the OS itself, where some of the slowness can at least be explained by the silo-ed nature of development and the large amount of moving parts. But even when MS gives a small-ish team free reign and a fresh start, the software is just agonizingly slow and buggy.

An example: new PowerToys https://github.com/microsoft/PowerToys/

The FancyZones "window snap" UI takes upwards of half a second to activate when dragging a window and the Zone Editor is at around 5s. All in all it is only very slightly less buggy than 3rd party tiling WMs like komorebic.

The PowerToysRun utility input is extremely variable, takes between 1 and 20(!) seconds. A lot of the plugins shipped with it simply don't work or have no suggestions/hints once you enter their prefix. The search relies on WindowsSearch, which is about 500x slower than https://github.com/sharkdp/fd and has not improved since Win7. Who cares, nobody ever searches for files, right? As a whole, PTRun is simply worse than https://github.com/Flow-Launcher/Flow.Launcher which uses the same UI kit as far as I can see. WTF?

[ljm]

The most frustrating thing with PowerToys is trying to remap keys (like caps lock to Ctrl). It feels like it's done by intercepting the keypress at runtime in the app rather than being configured at the system level, so if you happen to, say, hit your new Ctrl key when the CPU is pegged, it'll revert back to caps lock and then also get stuck. So you have to go into PowerToys to unbind the key, turn off caps lock, then rebind it.

There's another app that does this in the registry I think, but I keep forgetting the name of it.

[eco]

The registry method is Ctrl2Cap by SysInternals.

https://learn.microsoft.com/en-us/sysinternals/downloads/ctr...

It's the first thing I download whenever I'm setting up a new Windows machine.