GitHub Atom

» see atom.io as it lived, on the wayback machine

~ the obituary ~

atom showed up in my editor rotation around 2014, somewhere between sublime text 2 (which was closed source and had a polite license nag) and whatever vim setup i had at the time. the pitch on the homepage was "a hackable text editor for the 21st century," and the thing it was actually selling was that the editor itself ran on chromium and node, which meant you could write packages in javascript and css the same way you wrote anything else. for an engineer that was a real selling point and also the reason it eventually died.

github started atom internally as a chris wanstrath side project around 2008. it shipped as a public beta in february 2014 and hit 1.0 in june 2015. electron, the framework underneath it, got pulled out and named separately, which is what then allowed slack and discord to ship cross-platform desktop clients without doing native work. an entire generation of electron desktop apps followed. that downstream story is bigger than atom itself.

microsoft bought github in 2018. visual studio code shipped on the same electron stack atom had open-sourced, with the same extensibility model and a more focused team behind it. by 2020 vs code was eating the entire developer-editor market. on june 8 2022 github announced atom's end of life, and on december 15 2022 the repos were archived.

~ the case file ~

~ how it landed ~

the architectural choice that defined atom also limited it. running an editor inside a chromium instance meant every keystroke had to go through a layout engine designed for web pages, which translated into noticeable lag on big files. the team spent years optimizing it and made real progress, but sublime text and later vim setups stayed faster on anything over a few thousand lines.

extension culture grew up around it anyway. the package registry was full of themes and linters, and you could install almost anything else as a plugin in a few clicks. for the window where atom was the default modern editor on github's homepage, that registry was the most active english-speaking editor-plugin community on the web. vs code inherited the audience and the muscle memory directly.

~ what it became ~

the community fork pulsar still ships releases as of 2026, run by volunteers off the original 1.60 codebase. zed, started by former atom lead nathan sobo, took the lesson from the chromium-lag problem and rewrote the whole editor in rust on a custom gpu-rendered ui stack. zed is the actually-interesting successor and pulsar is the polite continuation of atom-the-product.

electron meanwhile won everything. github could kill atom because vs code existed, and vs code existed because atom open-sourced the runtime that made it possible. the eulogy writes itself: the project was killed by its own technology choice.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »