Either way it doesn't matter. As someone who has used Windows in a significant way since the 90s, the taskbar and start menu are a buggy mess. The new design is awful, I just want a list of my programs like before.
No, Windows Start does not use React
11–20 of 64 posts
Re: No, Windows Start does not use React
#12Fatal error by the author: They’re right, it doesn’t use React in the way that everyone actually means and criticises. It still technically uses React though, so—as is already evident—you still get the worst of the worst, bad-faith arguers saying “WELL ACKSHULLY…”
Re: No, Windows Start does not use React
#13>Windows Start does not use React Ok >This is the part of the Windows Start that uses React. Ok
Sure, slightly inaccurate title, but the point they're making is valid, this comment isn't really a substantive critique. I could be wrong but I feel like when most HN commenters say that something "uses React" and also imply that that's a bad thing, what they really mean is "it loads a full web rendering engine and consumes ~200mb of unnecessary ram". Neither of those things are true here.
This is incorrect. It is a full JavaScript framework in your start menu.
I don't see your read that it's about ram-hungry web views either. To me, "Start menu uses React" is a dig that Microsoft is so uncommitted to it's native development platform that they (partially) don't use it in one of the most 'core' parts of the operating system.
Re: No, Windows Start does not use React
#14Re: No, Windows Start does not use React
#15Re: No, Windows Start does not use React
#16> This is the Windows 11 start menu. See that Recommended section at the bottom of it? That is built with React Native for Windows. No, that is not a full JavaScript framework in your start menu. There’s no web view / browser running gobbling up your resources. It’s React Native for Windows which is a flavor of React Native that directly calls Windows APIs including, you guessed it, WinUI 3. I would still say that me…
React Native, absolutely - as with Office 365, using WinUI 3 as the underlying UI layer.
Re: No, Windows Start does not use React
#17>Windows Start does not use React Ok >This is the part of the Windows Start that uses React. Ok
Sure, slightly inaccurate title, but the point they're making is valid, this comment isn't really a substantive critique. I could be wrong but I feel like when most HN commenters say that something "uses React" and also imply that that's a bad thing, what they really mean is "it loads a full web rendering engine and consumes ~200mb of unnecessary ram". Neither of those things are true here.
But we'll always hear "it's React!". Like most things, the masses must feed on the Internet outrage without critical thought.
Re: No, Windows Start does not use React
#18>It’s React Native for Windows which is a flavor of React Native that directly calls Windows APIs including, you guessed it, WinUI 3. >So that’s it. Windows Start has a very small section (that can be disabled) that’s written in a framework that follows React principles and compiles down to native code. False. React Native doesn't "compile down to native code". It runs actual JavaScript, just not inside a browser, bu…
Re: No, Windows Start does not use React
#19Earlier quoted context omitted.
Sure, slightly inaccurate title, but the point they're making is valid, this comment isn't really a substantive critique. I could be wrong but I feel like when most HN commenters say that something "uses React" and also imply that that's a bad thing, what they really mean is "it loads a full web rendering engine and consumes ~200mb of unnecessary ram". Neither of those things are true here.
> That is built with React Native for Windows. No, that is not a full JavaScript framework in your start menu. This is incorrect. It is a full JavaScript framework in your start menu. I don't see your read that it's about ram-hungry web views either. To me, "Start menu uses React" is a dig that Microsoft is so uncommitted to it's native development platform that they (partially) don't use it in one of the most 'core'…
If it fits and meets the goals of the project, why not?
Re: No, Windows Start does not use React
#20Earlier quoted context omitted.
Sure, slightly inaccurate title, but the point they're making is valid, this comment isn't really a substantive critique. I could be wrong but I feel like when most HN commenters say that something "uses React" and also imply that that's a bad thing, what they really mean is "it loads a full web rendering engine and consumes ~200mb of unnecessary ram". Neither of those things are true here.
Exactly this. And it is on a portion of the Start menu that can be fully disabled. Heck, my start menu looks like the Windows 10 start menu (yes, this is OOTB) as I wasn't fond of the "new" look of the Windows 11 start menu. But we'll always hear "it's React!". Like most things, the masses must feed on the Internet outrage without critical thought.
I mean, with tons of effort and config Windows can be turned into a usable OS. Needing to do all that is a huge part of the problem.