Why is Electron actually good for desktop apps?

TL;DR

Electron is a practical tool that lets developers ship cross platform desktop apps from a single code base. It enables rapid development for Windows, Mac and Linux, and famous apps like VS Code prove its potential. The video argues that the hate around Electron is overblown and explains the benefits and drawbacks.

Transcript

we need to have a conversation about electron I see it getting so much hate and I'll be real it doesn't deserve most of it electron as a technology isn't just important it's actually pretty good and I think these misconceptions about how electron is used and the bad electron Ops we all experienced have resulted in a negative sentiment that just isn... Read More

Key Insights

• Electron enables cross platform development with a single code base that works on Windows, Mac, and Linux.
• The origin of Electron traces back to Atom, which used a Chrome shell to allow web tech based editors to run as desktop apps.
• VS Code and other Microsoft projects helped show that Electron is not inherently bad, it can power high quality editors.
• Many popular apps like Slack, Discord, and Notion have used Electron to ship desktop experiences quickly.
• The cost of Electron includes duplication of Chrome components which can impact performance and resource use.
• Electron is valued for fast shipping and easier plugin ecosystems for web developers turned desktop app builders.
• Mac users sometimes criticize Electron apps for not feeling like native Mac software, highlighting design and performance expectations.
• The video frames Electron as a stepping stone that enabled improvements and new native style apps built on its ideas.
• More videos from this channel:
  • How to evaluate Opus 5 performance and cost effectiveness
  • How did Blue Sky become number one and stay open source
  • What could replace Git for collaborative coding?
• More from this channel: Theo - t3․gg

Questions & Answers

Q: What is Electron and where did the name come from?

Electron started as a way to build Atom, an editor from GitHub, using a Chrome shell so web based technologies could power native like cross platform apps. The name Electron comes from part of Atom, reflecting the atomic metaphor of its architecture and the idea that electrons are parts of matter within the Atom project.

Q: Why did developers choose to build Electron based editors and apps?

Developers chose Electron because it allows building software quickly for the web and for all desktop platforms with one code base. This meant teams could create desktop apps without rewriting native code for Windows, Mac, and Linux, and web developers could contribute plugins and features using familiar technologies.

Q: Which popular apps are built on Electron according to the video?

The video lists several well known Electron apps including Slack, Discord, Teams, WhatsApp, Skype, Visual Studio Code, Atom, GitHub Desktop, Postman, Figma, Notion, Obsidian and WordPress Desktop. These examples illustrate Electron’s reach across productivity, collaboration, and design tools.

Q: What are the main criticisms of Electron mentioned in the talk?

Critics argue that Electron apps duplicate large browser components, leading to higher memory and storage use. There is concern about performance, particularly on Mac where users expect native feel and optimization. The talk also notes that Electron can be perceived as not feeling like truly native software and can be heavy for some workflows.

Q: How did VS Code influence perceptions of Electron?

VS Code showed that an Electron based editor could be extremely capable and popular. Despite Electron, the editor achieved high performance and usability, supporting a robust extension ecosystem. This demonstrates that Electron itself is not inherently a limitation on quality or capability, as long as development practices and optimization are well managed.

Q: What historical context about Atom and Chrome shells is provided?

The video explains that Atom used a stripped down Chrome shell to run the editor as a desktop app with web technologies. This shell later evolved into what is now Electron, and the history frames Electron as a continuation of Atom's approach rather than a fundamentally flawed concept.

Q: What is one major future consideration for Electron mentioned?

A major consideration is balancing the benefits of rapid cross platform development with resource usage and native feel on macOS and other platforms. The talk hints that while Electron offers strong value for fast shipping, there is ongoing discussion about optimization and how to maintain performance as apps scale.

Q: Why should people rethink the hate toward Electron according to the video?

The speaker argues that Electron’s advantages in speed, cross platform support, and accessibility for web developers make it a compelling choice in many scenarios. The negative sentiment is framed as overblown, as seen in high quality apps built on Electron and the practical benefits of shipping features quickly across platforms.

Summary & Key Takeaways

• Electron enables cross platform desktop apps from one code base, speeding development across major operating systems.

• The video highlights that popular apps like VS Code and GitHub Desktop demonstrate Electron's viability despite criticism.

• The speaker argues that the negative sentiment toward Electron is unfair and discusses scenarios where it is a strong choice.