An Editor Eating Its Own Dog Food
GitHub released Atom in February 2014 as an open-source text editor built for the workflows its own engineers already lived inside. The underlying runtime — then called Atom Shell, later renamed Electron — wrapped Chromium and Node.js into a desktop application container, letting the team write editor logic in JavaScript and CoffeeScript rather than native platform code. It was a deliberate architectural bet: that web technologies were good enough to drive a professional tool.
The package system reflected the same philosophy. Atom's configuration and extensions were written in CoffeeScript and loaded at startup through a package manager (apm) that drew from a public registry. At peak, thousands of community packages covered syntax highlighting, linters, Git integration and language support across dozens of ecosystems. The editor shipped under the MIT licence, which meant every package author worked within the same permissive terms as the host.

The bet attracted users quickly, but it also attracted criticism. Startup time and memory consumption lagged behind native editors, a cost the Electron layer imposed regardless of package count. When Microsoft shipped Visual Studio Code in April 2015 — also built on Electron, but with incremental compilation of TypeScript driving its language tooling — the comparison sharpened the tension. VS Code was faster, shipped with a built-in debugger, and eventually won the Language Server Protocol ecosystem almost entirely.
GitHub announced in June 2022 that Atom would be archived on 15 December 2022, citing the maturity of the alternatives its own infrastructure had helped create. The repository was archived rather than deleted, preserving the codebase for inspection. Electron, the durable contribution, continued under the OpenJS Foundation and remained the runtime beneath dozens of desktop applications. Atom's package registry went dark with it, but the architectural pattern — a web-technology core, a permissive licence, a public extension marketplace — had already been inherited by successors with the resources to sustain it.
