AI summary by TwinMind
Is Electron really that bad?
Theo - t3․gg
37m 40s
Introduction & Sponsor
- Video defends Electron against widespread criticism
- Claims misconceptions about Electron usage result in unfair negative sentiment
- Sponsor: Blacksmith - GitHub build optimization tool
- 25GB cache vs 10GB standard
- 4X network speeds (4 Mbps vs 100)
- 2X faster code execution than GitHub Runners
- PostHog reduced build times from 8:38 to 1:27 minutes
- 1/10th the price
- Supports Docker builds, 40X faster storage
- Custom caching for Go, Node, Python, Ruby, Zig
Electron History & Origins
- Atom editor created by GitHub as major IDE shift
- Before Atom: fragmented editor landscape (Sublime Text, Vim, JetBrains)
- GitHub team were front-end devs, didn't know native app development
- Created stripped-down Chrome shell to build editor using web technologies
- Atom wasn't fast but had excellent extensibility
- Electron extracted from Atom project (atoms → electrons naming)
- Atom now discontinued but Electron lives on
VS Code Success Story
- Microsoft saw Atom's potential despite quality issues
- Built VS Code using Electron with superior development team
- Proved Electron wasn't the problem with Atom
- VS Code became one of best editors ever made
- Demonstrated that tool quality depends on developers, not framework
Current Electron Adoption
- 115,000 GitHub stars (top 5-10 most starred projects)
- Major apps using Electron:
- Communication: Slack, Discord, Teams, WhatsApp, Skype
- Development: VS Code, Atom, GitHub Desktop, Postman
- Design/Productivity: Figma, Notion, Obsidian, WordPress Desktop
- Others: 1Password, Bitwarden, Twitch Desktop (deprecated)
Why Electron Got Popular
- Enables building software quickly for web + all desktop platforms
- Single codebase approach
- Web developers can build desktop apps without learning native development
- Companies could ship desktop apps that otherwise wouldn't exist
- Democratized desktop app development
Common Criticisms of Electron
Not Native Feeling
- Apps don't feel like platform-native software
- Inconsistent menu bar behavior across Electron apps
- Different interaction patterns between apps
Performance Issues
- JavaScript inherently slower than native code
- Multiple Chrome instances running simultaneously
- Significant memory/CPU overhead
Enables Worse Software
- Companies ship lower quality software faster
- Web page updates make software more fragile
- Results in buggier, less reliable applications
Counter-Arguments to Criticisms
Native Feel Argument Invalid
- Modern native apps (including Apple's) don't feel truly native anymore
- Apple's Journal app lacks basic native functionality
- Native software quality has declined over past decade
- Mac OS improvements stagnated except for processor upgrades
- Native feel concept meaningless when native software is poor quality
Performance Misconceptions
- Developer quality matters more than framework choice
- Estimated only 5% of developers care about software quality
- Bad developers gravitate toward popular tools (including Electron)
- Popularity breeds low-quality implementations
- No technology escapes this cycle once popular enough
Performance Reality Check
- Electron apps can outperform native apps in many cases
- Example: Native Swift UI chat apps struggle with real-time rendering
- Native chat GPT apps hit 100% CPU with 2000+ character messages
- Chromium team spent decades optimizing text/document rendering
- Well-written Electron apps often faster than equivalent native apps
- Spotify (Electron-based) uses <3% CPU
Developer Quality Distribution
- Visual representation: majority of developers are average/poor quality
- Popular frameworks inevitably used by bad developers
- Electron's popularity means more bad developers use it
- Framework choice doesn't determine software quality
- Bad developers create bad software regardless of tools
Linux and Cross-Platform Benefits
- Electron enables first-time real software availability on Linux
- Chromium team handles cross-platform compatibility (Windows, Mac, Linux flavors)
- Wayland transition supported by Chromium team
- Single codebase works across all platforms with identical user experience
- Google Chromebooks prove Linux viability through web platform
- Linux desktop success depends on Electron/Chromium technologies
- Community builds wrappers around websites using Electron
Alternative Technologies
Tauri
- Rust-based alternative to Electron
- Uses JavaScript for UI, Rust for system operations
- JSC-based (not Chromium), smaller/lighter but less stable
- Best for Rust developers adding UI to existing Rust applications
- Lacks ecosystem of packages compared to Electron
- Not suitable for JavaScript developers wanting desktop apps
React Native Desktop
- React Native Windows (official Microsoft package)
- React Native macOS (also Microsoft-maintained)
- Microsoft admits native Windows development tools are poor
- Major Microsoft apps use React Native (Outlook, Calendar, Xbox UI, Windows 11 Start button)
- Renders truly native components (not web views)
- Missing Expo-equivalent for easy development setup
- Future looks promising for desktop development
Performance Nuance
- Performance differences between frameworks often negligible
- Multiple factors affect performance beyond framework choice
- Native doesn't automatically mean faster
- Web rendering can outperform native UI frameworks
- Decision shouldn't be based solely on performance assumptions
Conclusion & Appreciation
- Electron team deserves praise, not criticism
- Enabled Mac users to have good software
- Prevented Linux users from being left behind
- Allows developers to ship great software to all desktop platforms
- Criticism should target bad developers/companies, not the technology
- Electron essential for software ecosystem health
