Comment by felixgallo
4 days ago
Whatever product manager team decided to jump into React Native with both feet for the Windows experience needs to be ejected from the industry permanently. Think of how many thousands of human hours per day are now spent waiting on React Native jank, all in order to save the Windows developers from having to program in Windows using Microsoft products.
Most likely saving Windows developers from learning programming. They are just javascript monkeys because that is what Microsoft is hiring these days and you can't trust monkeys with native C++. The thing would leak memory and explode immediately if those idiots tried to write native code. So in the name of hiring cheap idiots that can't program we all have to put up with this slow, bloated garbage.
There is no universe in which I should see lag between a click and a menu appearing in File explorer, taskbar or anywhere in the OS. Not on a machine with 8 idling cores.
> So in the name of hiring cheap idiots that can't program we all have to put up with this slow, bloated garbage.
Irony is they're not cheap hires, either.
MS could/should have just made other XAML/MAUI options a better experience in general over the React Native thing... It might be different if they actually embrace web as a whole and at least gave a consistent UX, more like say WebOS or ChromeOS, but that's not what they're doing here.
What MS really needs to do is create a really long checklist of all the UI defained configurations and options, along with a connected list of all the relevant API interfaces they connect to... then come up with a consistent, complete and competent component library to do a ground up re-implementation of all the things in a consistent way.
This would, of course mean stabilizing the released version of windows to mostly bug fixes for a couple years while frantically generating and dog-fooding the new UX... starting with a re-revamped task manager, and launcher/file-picker. Just a bare desktop and a hotkey that opens task manager as the first and only UI elements then working out from there.
It's a nice thought but think of the cost!
You do have to wonder what the hell the people in charge of the Windows UI are thinking. They seem to have got it so badly wrong. But so has Apple in macos.
I'm not sure the cost would be significantly worse than all the half-assed abandoned efforts so far... and it would result in the first consistent UX in Windows since Win2k.