What absolute scares me is how even if you download Windows Enterprise IoT, which already comes extremely clean out of the box, and then run your favorite debloating script (removing even more crap)… the system still shows a noticeable delay when opening the right click menu, or the start menu, or a new Explorer window. So the most basic possible tasks, that you do constantly, for some reason are slow on a modern multi-core processor and a clean build of the OS.
How the hell did they manage to downgrade… the start menu? the right click menu? How?
They’re likely using react native (Microsoft has pretty much gone all in on react for new ui things). It’s not as crazy as it sounds, the majority of cross platform mobile apps use react native.
It’s important to note that it’s not a web browser that’s rendering the ui. The way it works is that react native provides a way for js logic to define the ui declaratively (kinda like HTML), then react native calls platform native components to do the actual rendering. So you declare <Button> and what comes out on the other end is a real, genuine windows-provided button.
What absolute scares me is how even if you download Windows Enterprise IoT, which already comes extremely clean out of the box, and then run your favorite debloating script (removing even more crap)… the system still shows a noticeable delay when opening the right click menu, or the start menu, or a new Explorer window. So the most basic possible tasks, that you do constantly, for some reason are slow on a modern multi-core processor and a clean build of the OS.
How the hell did they manage to downgrade… the start menu? the right click menu? How?
I read they’re using react, the JavaScript library, for the start menu. If true that strikes me as insane
They’re likely using react native (Microsoft has pretty much gone all in on react for new ui things). It’s not as crazy as it sounds, the majority of cross platform mobile apps use react native.
It’s important to note that it’s not a web browser that’s rendering the ui. The way it works is that react native provides a way for js logic to define the ui declaratively (kinda like HTML), then react native calls platform native components to do the actual rendering. So you declare
<Button>and what comes out on the other end is a real, genuine windows-provided button.