Atom was archived today
github.com
Atom was archived today
1–10 of 614 posts
Re: Atom was archived today
#2Re: Atom was archived today
#3Re: Atom was archived today
#4Re: Atom was archived today
#5Re: Atom was archived today
#6Re: Atom was archived today
#7The Atom developers made some technology choices that in retrospect were ill-advised, CoffeeScript being the worst of them and splitting everything into dozens of packages a close second. They tried to backpedal on both of these later on, but by that time VSCode, with its far superior engineering built around TypeScript, was rapidly taking over.
Of course, the GitHub acquisition was the last straw, but to be fair Atom was already pretty dead by then.
While the Atom project ultimately failed, it did give us Electron and Tree-Sitter, two technologies that will certainly outlive it.
Re: Atom was archived today
#8I also tried VSCode, but was never really quite able to get into the interface the same way. For a while I tried customizing the interface with plugins like CustomizeUI, but Microsoft broke those recently, and I've been happier with Sublime.
Re: Atom was archived today
#9I had a lot of fun whipping up plug-ins within minutes for Atom! It let me try out ideas very quickly.
In my mind, emacs suffers the same problem as TeX/LaTeX. Some parts of it are very antiquated and just don't fit into the modern world anymore. They'd need an overhaul.
But, that overhaul is hard to impossible to do without losing compatibility. And that compatibility is why you simply cannot replace emacs or LaTeX: There is many decades of features, packages, and whole ecosystems in there. Throwing that away would be a giant loss, people will always continue using it. Other editors can't catch up. Maybe if they survive for ~50 years, too?
Just to drive home how old emacs is: At one point, the popular joke was that emacs stands for "eight megabytes and constantly swapping". Yep, 8MB large software was so bloated that it was funny and debilitating.
Re: Atom was archived today
#10Sad to see this go. I was an early adopter of Atom, and I wrote two extensions for it, one of which while it was still in beta. The Atom developers made some technology choices that in retrospect were ill-advised, CoffeeScript being the worst of them and splitting everything into dozens of packages a close second. They tried to backpedal on both of these later on, but by that time VSCode, with its far superior engine…