AI summary by TwinMind
Microsoft Regrets Using React (For Edge)
Theo - t3․gg
14m 28s
Microsoft Edge Performance Issues & Context
- Edge built around Chromium with UI pieces using HTML/JavaScript/React
- Each UI element (menus, dropdowns, favorites tab) = separate mini React apps
- Not one giant React app, but multiple React instances sharing common bundles
- Problem: React apps for static UI that rarely changes = performance bottleneck
Performance Improvements Delivered
- Edge 122: Browser Essentials UI 42% faster for regular users, 76% faster for devices without SSD or <8GB RAM
- Edge 124: Favorites feature 40% faster (expanded/collapsed states)
- Future improvements planned: history, downloads, wallet features
Root Cause Analysis via Telemetry
- Edge monitors UI responsiveness through end-user telemetry data
- Research shows specific absolute responsiveness targets needed for "fast" perception
- Data revealed opportunities for lower-resource device improvements
- Key findings:
- Code bundles too large for components
- Non-modular UI code organization
- Teams sharing common bundles unnecessarily
- Client-side rendering causing delays (download → JIT compile → execute → render)
Microsoft's React Native Strategy Context
- Microsoft heavily invested in React Native for Windows/Mac
- Built to address Windows-only development limitations
- Used across: Xbox store, Windows 11 start menu, Office suite components
- React Native for Windows runs on Windows, Mac, Xbox
- Allows building once for all desktop platforms
- Uses JavaScript to control native platform UI elements (not HTML rendering)
Web UI 2.0 Architecture Solution
- New "markup first" architecture minimizing bundle sizes
- Reduces JavaScript execution during UI initialization
- More modular design with performance-tuned web components repository
- Web platform patterns for new browser features within markup-first approach
- Browser Essentials = first feature converted to test new architecture
- Plans to upgrade more Edge UI components over time
- Plans to open source some packages
Technical Implementation Details
- Moved from client-side rendering to server-side rendering approach
- Uses HTML/CSS for faster rendering (pre-Web 2.0 era approach)
- Modern browser engines fast at rendering when JavaScript doesn't interfere
- Web components repository for reusable UI elements
- Contradiction noted: web components can't be server-side rendered traditionally
Criticism & Analysis Points
- Article reaches beyond Edge-specific improvements to critique JavaScript UI rendering generally
- Problem was multiple React instances, not React itself
- React Native could have solved original problem with single JavaScript engine
- Chrome uses C++ for UI, Firefox uses HTML/CSS
- Microsoft simultaneously embraces React Native elsewhere while criticizing React here
