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.
