Atom: the hackable text editor that accidentally built a platform
Nathan Sobo had been thinking about text editors since 2005, when he wrote a parsing framework for Ruby called Treetop and imagined what might come after it. Nothing did — until a company party in San Francisco around 2011, where he found GitHub co-founder Chris Wanstrath long enough to make the pitch (Changelog, ep. 241). Wanstrath, it turned out, was already thinking along similar lines: he and engineer Cory Johnson had been prototyping something using the Ace editor engine inside a browser viewport. When Sobo joined GitHub, the two threads merged.
The missing piece was infrastructure. No framework existed for building a desktop application from web technologies that could also reach the file system and spawn processes. Sobo contracted a developer named Cheng, from Intel’s research lab, with a single mandate: make Node.js APIs and the browser DOM work together without friction. The result was called Atom Shell, and it was the engineering achievement that would outlast everything built on top of it.
On February 26, 2014, GitHub announced Atom in a closed beta for macOS: “a hackable text editor for the 21st century” (Wikipedia). The tagline was the entire argument. Where Sublime Text had made customization possible, Atom made it structural. Every part of the interface was a package — including the core editing surface. A developer with enough patience could rebuild the editor from scratch.
The team was small enough to list: Sobo, Kevin Sawicki, and Ben Ogle, who arrived with GitHub’s acquisition of Easel.io and, by Sobo’s account, transformed the project from experiment to product. Antonio Scandurra earned his spot by submitting such high-quality pull requests that the team eventually just hired him. GitHub opened the code, Atom Shell included, under the MIT License in May 2014.
That was the move that mattered most. In April 2015, Atom Shell was renamed Electron and released as a standalone framework. Within a year it was running Slack’s desktop client. Then Visual Studio Code. Then Discord, Signal, GitHub Desktop. Today the Claude and ChatGPT desktop applications run on Electron. The editor was always the visible part. The platform was the legacy.
Atom never caught the wave it created. Visual Studio Code launched in 2015 on the same Electron foundation, faster and better funded, and by 2018 had surpassed Atom in every survey. GitHub announced Atom’s end-of-life on June 8, 2022, citing VS Code and GitHub Codespaces as the future (Wikipedia). The shutdown came December 15 of that year.
Nathan Sobo went on to build Zed, written in Rust — native, fast, and deliberately not Electron. He called it the spiritual successor to what Atom might have been.
Atom shipped in 2014 and shut down in 2022. Electron shipped in 2014 and has not stopped. The thing Atom was standing on outlasted what Atom was for.
Sources
- Atom (text editor) — Wikipedia — launch timeline (February 2014 beta, May 2014 open source release), Electron origins, June 2022 end-of-life announcement and December 2022 shutdown.
- The Story of Atom with Nathan Sobo — Changelog Podcast #241 — Sobo’s first-person account of the party pitch to Wanstrath, the Treetop backstory, the team’s formation, and the contract with Cheng to build Atom Shell.
- Atom Shell is now Electron — electronjs.org — the April 2015 renaming announcement and rationale for spinning out as a standalone framework.