Brendan Eich Criticizes Windows 11 for Excessive Use of WebView2 and Electron
Hello HaWkers, Brendan Eich, the creator of JavaScript and founder of the Brave browser, has raised an important discussion about the future of desktop development. In recent comments, he criticized Microsoft for the increasing use of WebView2 and Electron-based frameworks in Windows 11.
The debate about native performance versus web technologies is hotter than ever, and the implications affect developers on all platforms.
What Brendan Eich Said
Eich did not spare criticism for what he calls Windows 11 "bloat":
Main points raised:
- Windows 11 is increasingly dependent on web interfaces
- Native applications are being replaced by Electron/WebView2 wrappers
- The result is excessive memory and CPU consumption
- User experience is degrading
- Microsoft prioritizes development speed over quality
💡 Context: Brendan Eich created JavaScript in 1995 at Netscape. Despite being the "father" of the language that runs Electron, he advocates for responsible use of web technologies.
The Problem With Electron/WebView2 Apps
To understand the criticism, you need to know how these frameworks work.
How Electron Works
Each Electron application loads:
- A complete instance of Chromium (browser)
- The Node.js runtime
- The JavaScript/HTML/CSS application code
- Libraries and dependencies
Typical impact of an Electron app:
| Resource | Native App | Electron App | Difference |
|---|---|---|---|
| RAM (idle) | 30-50 MB | 150-400 MB | 5-10x |
| Install size | 10-50 MB | 150-500 MB | 5-15x |
| Startup time | < 1s | 2-5s | 3-5x |
| CPU usage (idle) | < 1% | 2-5% | 3-5x |
Examples of Popular Electron Apps
Applications using Electron:
- VS Code (Microsoft)
- Slack
- Discord
- Figma Desktop
- Notion
- 1Password
- Postman
- Microsoft Teams
The Other Side of the Debate
Electron and WebView2 defenders also have valid arguments.
Advantages of Web Development for Desktop
Why companies choose Electron:
- One codebase, multiple platforms: Windows, Mac, Linux with the same code
- JavaScript ecosystem: Millions of libraries available
- Development speed: Significantly shorter time-to-market
- Hiring: Web developers are more abundant
- Maintenance: Updates easier to distribute
Recent Improvements
What changed in recent years:
- Electron 28+: Significant memory optimizations
- WebView2: Lighter than full Chromium
- Tauri: Lighter alternative using native webview
- Capacitor: Another option for hybrid apps
The Impact on Windows 11
Eich's criticism reflects a visible trend in Microsoft's system.
Web Components in Windows 11
Parts of Windows using web technologies:
- Widgets (WebView2)
- Settings (partially)
- Microsoft Store
- Various system applications
- Cloud service integrations
Users Notice the Difference
Common complaints:
- Operating system slower than Windows 10
- Higher RAM consumption at idle
- Applications take longer to open
- Laptop battery drains faster
- Fan runs more frequently
Alternatives and Solutions
The market is responding with lighter options.
Tauri: The Rust Alternative
Tauri offers desktop apps using Rust on the backend and native webview:
Tauri vs Electron comparison:
| Metric | Electron | Tauri | Improvement |
|---|---|---|---|
| Binary size | ~150 MB | ~3-10 MB | 15-50x |
| RAM (idle) | ~200 MB | ~20-40 MB | 5-10x |
| Build time | Slow | Fast | 3-5x |
| Security | Good | Excellent | Rust memory safety |
Other Alternatives
Options for desktop development:
- Flutter Desktop: Google, Dart, good performance
- React Native Windows: Microsoft, JavaScript, real native
- .NET MAUI: Microsoft, C#, cross-platform
- Qt: C++, excellent performance, complex license
What This Means For JavaScript Developers
The debate raises important questions about technology choices.
When to Use Electron/WebView2
Cases where it makes sense:
- Rapid prototyping
- Internal company apps
- Products needing multiple platforms
- Teams with primary web experience
- MVPs and idea validation
When to Consider Alternatives
Cases where performance matters more:
- Productivity applications used hours per day
- Developer tools
- Apps running in background
- B2C products where UX is critical
- Systems with limited resources
Skills to Develop
To stay relevant:
- Performance optimization: Understand where JavaScript is slow
- Rust/Tauri: Growing alternative
- WebAssembly: Bridge between web and native performance
- Profiling: Identify bottlenecks
- Native bindings: Call native code when necessary
The Future of Desktop Development
The debate between native and web will not end, but the trend points to a middle ground.
Emerging Trends
What to expect:
- WebAssembly gaining space in desktop apps
- More efficient hybrid frameworks
- Greater pressure for performance in Electron apps
- Native APIs more accessible via JavaScript
- Development tools improving optimization
Lessons For Developers
Practical takeaways:
- Performance matters and users notice
- Convenience has a cost - know the tradeoffs
- Alternatives exist - evaluate before choosing
- The market is evolving - stay updated
- Fundamentals matter - understand what happens "under the hood"
Conclusion
Brendan Eich's criticism is not against JavaScript or web technologies - it is against their irresponsible use. As the language creator, he knows better than anyone its capabilities and limitations.
For JavaScript developers, the message is clear: know your tools, understand the tradeoffs, and choose the right technology for each problem.
If you want to dive deeper into how JavaScript is evolving to solve some of these problems, I recommend checking out the article about JavaScript Signals: The Native Pattern That Will Revolutionize Web Reactivity where you will discover optimizations coming to the language.