AFAIK, React is a Single-Page Web Application that refreshes everytime something changes. It's benefits are fast load times and lower overhead because it ONLY updates things that are changed on re-render, but the downsides are that it relies on other libraries for things like multiple pages, etc.
So for it to be a Windows System application, yes that's fucking attrocious. Did you ever hear how angry people were about the Warcraft 3 update that added a bunch of webapp nonsense and bricked a lot of people's old copies? Well, that's basically what Windows 11 did.
Small nitpicks: The point of react is that it DOESN'T refresh. It maintains a virtual DOM which is faster to update and diff than the regular browser DOM, which you hinted at. No libraries necessary to do routing, but they do make it easier and better.
This however is a React Native application which doesn't have the same (browser) backend or requirements. It's native code. There is no refresh or routing per se.
That all said, the start menu is an abomination of the highest order. It just isn't really React's fault. People just love to hate on React and . React also gets a bad rap because it's so ubiquitous and easy to start using that novices and morons alike can make atrociously slow, bloated web apps with it.
React Native can be built for, not only mobile targets, but multiple platforms, such as Windows, tvs,..., or even the web, trying to use as much native implementations as possible.
Now, should you?, that's a different discussion...
Okay, the cross platform part makes it make a little sense. They're trying to push everything over to arm (again!) and having something easy to cross compile would help..... But, you know .... The start menu is small potatoes compared to gestures at the rest of Windows ...
AFAIK, React is a Single-Page Web Application that refreshes everytime something changes. It's benefits are fast load times and lower overhead because it ONLY updates things that are changed on re-render, but the downsides are that it relies on other libraries for things like multiple pages, etc.
So for it to be a Windows System application, yes that's fucking attrocious. Did you ever hear how angry people were about the Warcraft 3 update that added a bunch of webapp nonsense and bricked a lot of people's old copies? Well, that's basically what Windows 11 did.
Small nitpicks: The point of react is that it DOESN'T refresh. It maintains a virtual DOM which is faster to update and diff than the regular browser DOM, which you hinted at. No libraries necessary to do routing, but they do make it easier and better.
This however is a React Native application which doesn't have the same (browser) backend or requirements. It's native code. There is no refresh or routing per se.
That all said, the start menu is an abomination of the highest order. It just isn't really React's fault. People just love to hate on React and . React also gets a bad rap because it's so ubiquitous and easy to start using that novices and morons alike can make atrociously slow, bloated web apps with it.
I'm confused though. The op says "react native", but AFAIK, react native is a mobile app framework.
Does it work/deploy on desktop now?
React Native can be built for, not only mobile targets, but multiple platforms, such as Windows, tvs,..., or even the web, trying to use as much native implementations as possible. Now, should you?, that's a different discussion...
Okay, the cross platform part makes it make a little sense. They're trying to push everything over to arm (again!) and having something easy to cross compile would help..... But, you know .... The start menu is small potatoes compared to gestures at the rest of Windows ...
Yes, there's support for compiling React Native to UWP apps for Windows. No, I don't know why anyone thought that was a good idea.