When the Windows 11 start menu is just another React Native component
Description
Screenshot of a Twitter thread in dark mode. Tweet 1 by Philippe Tremblay (@philtrem22) reads: “Hi Daniel, I'm the guy responsible for implementing the start menu with React Native in Windows 11. Lemme know if you have any questions.” Tweet metrics show 9 replies, 127 likes, 15.1 K views. Tweet 2 by Daniel (@growing_daniel) replies: “first question why” (4 replies, 312 likes, 7 K views). Tweet 3, Philippe responds: “I’m a React developer so it only made sense. Any other questions?” (5 replies, 102 likes, 4.5 K views). Tweet 4 by Aadit (@SwagDoctor19) asks: “what was the performance consideration for such an implementation?” (1 reply, 24 likes, 3 K views). Tweet 5, Philippe answers: “I try not to let such considerations get in the way of doing great work.” (5 replies, 170 likes, 3 K views). Visually, each tweet is stacked with avatar circles on the left, blue verification ticks, and interaction icons below. Technically, the meme pokes fun at choosing React Native for a core OS component, highlighting over-engineering, framework bias, and ignored performance trade-offs that veteran engineers love to debate
Comments
22Comment deleted
Proof that if the only tool you have is npm, every OS shell begins to look like a node_modules folder
This perfectly captures the 'when you're a React developer, everything looks like a component that needs 300MB of node_modules' - though I'm still not sure if Philippe is satirizing Microsoft's actual architectural decisions or if this is the most elaborate way to explain why my Start Menu takes 3 seconds to render a list of 12 apps
When your entire architectural decision-making process is 'I'm a React developer so it only made sense' and performance considerations are just obstacles to greatness, you know you've achieved peak modern software engineering. Nothing says 'enterprise-grade OS component' quite like shipping a JavaScript runtime with your Start Menu - at least the inevitable memory leaks will give users a reason to reboot regularly, maintaining that classic Windows experience
Pressing the Windows key shouldn’t trigger a hydration cycle, but hey - nothing embodies resume‑driven architecture like a system shell that needs a JS runtime before you can click Shut Down
Performance considerations? In React, we just add React.memo to the boot screen and call it optimized
Classic RDD: pick React Native for the Windows Start menu because 'team expertise,' then wonder why the JS bridge turns click‑to‑open into an IPC benchmark - SLOs downgraded to eventual responsiveness
React developers are so sick in the head they'd code an entire operating system in react if they could Comment deleted
https://www.windows93.net Comment deleted
The only thing that prevent this motherfuckery is their incompetency Comment deleted
Vscode exists. Pretty much an operating system. Comment deleted
Oh so that is what is wrong with Windows 11. Makes sense. Comment deleted
I love how we have like 5+ layers of different UI systems stacked on top of each other in Win11, too. Comment deleted
It wouldn't be so bad if Microsoft would deprecate and remove old stuff Comment deleted
But if they did, there'd be huge holes in critical parts of their management UI. :D Comment deleted
Good luck trying to set your environment variables if you got rid of the comdlg32.dll era crap. Comment deleted
Only the "Recommended" section is written in React Native, which still uses WinUI. It's not a big deal and no, cpu does not spike in any way that matters when you press the Windows key Comment deleted
my computer turns into a toaster just by starting windows system. while I can start and update my Linux setup without fans accelerating to even half of the speed. I think the whole system was programmed without performance considerations. Comment deleted
Is it true?... Comment deleted
Just use open shell https://open-shell.github.io/Open-Shell-Menu/ Comment deleted
Dude needs to get shot Comment deleted
Is this legit Comment deleted
I get a cpu usage spike ok all cores from 30% idle to 70% just when opening start menu because of this fucking idiot Comment deleted