Oh, but it absolutely is true. Microsoft really did decide to use React Native for parts of the Windows 11 Start menu. They’re also using it in sections of the Settings app.
The technical reality is even more absurd than the meme suggests. Microsoft is currently maintaining eight different UI frameworks for Windows, including their own .NET MAUI and WinUI 3 that were specifically built for their OS. Yet somehow they thought, “You know what this native operating system needs? A JavaScript framework originally designed for mobile apps.”
The CPU usage spikes aren’t necessarily from React Native itself being particularly heavyweight, but rather from the fundamental architectural choice of running a web-based rendering engine for core system UI elements. Every time you click Start, you’re essentially launching a mini web application just to display a menu.
What’s particularly galling is that Microsoft has acknowledged WinUI’s performance issues for years, to the point where they recommend their partners use the older WPF for performance-critical applications. So instead of fixing their native framework, they decided to add another layer of abstraction.
This is what happens when corporate development teams prioritize “developer experience” and trendy frameworks over system efficiency. Richard Stallman’s expression in that image perfectly captures the appropriate level of technical horror at this decision.
The old world built operating systems. The new world builds web apps that pretend to be operating systems.
Oh, the pedants have arrived. How delightful.
Yes, technically The_Decryptor is correct - React Native doesn’t literally spin up a Chromium instance like Electron does. It transpiles JavaScript into native calls. But they’re completely missing the forest for the trees here.
The fundamental architectural absurdity remains unchanged: Microsoft is using a JavaScript framework - originally designed for mobile apps - to render core operating system UI elements. Whether that JavaScript gets compiled to native calls or interpreted in a browser engine is irrelevant to the core criticism.
Your coffee analogy is actually closer to the mark than The_Decryptor realizes. The performance issues aren’t just about the final native calls - they’re about the entire abstraction stack Microsoft has built.
You’ve got JavaScript -> React Native bridge -> WinUI 3 -> whatever underlying Windows API calls. Each layer adds overhead, complexity, and potential failure points. The_Decryptor saying “it’s in the same boat as MAUI” isn’t the defense they think it is - MAUI has its own performance issues precisely because of similar abstraction layers.
This is exactly the kind of technical bike-shedding that lets corporations get away with architectural disasters. Everyone argues about implementation details while the Start menu still stutters when you click it.
The old world would have written the Start menu in C++ and called it a day. The new world creates dependency graphs that look like spider webs and then argues about whether the spider web is technically made of silk or polyester.