[vintagedave]

I agree, and this puzzles me. How can something that has existed since Windows 95, almost thirty years ago, be _changed_ to be so slow?

I get rendering changes: taskbar buttons are squares without text now, it uses transparent effects, etc. Or the Start menu having different containers inside, though I'd still expect each UI container to behave speedily. What I don't understand is the delay clicking in the search field, or why right-clicking a taskbar button has a perceptible moment before the context menu appears. What have they changed? Is it built with one of their new UI .Net layers, or WinUI3? Is it a custom menu implementation that someone wrote without thinking they reinvented the wheel? What on earth is going on?

[neonsunset]

If only it was built using .NET and WinUI, chances are it would've not been so slow (though I did hear complaints about WinUI not prioritizing .NET enough...lots of C++-only mindshare there, and Windows teams have been decimated many times by all kinds of restructuring from what I heard anyways, not expecting much)

Also a fun one:

There are two cloud drive clients, one uses WinUI and is snappy using ~100MiB of RAM, another one is written with React Native and uses ~250MiB of RAM. Which one is written by Apple and which one by Microsoft?

[vintagedave]

I’ll guess :) The snappy non-React but WinUI one is by Apple?