Sunsetting Atom
github.blog
Sunsetting Atom
1–10 of 880 posts
Re: Sunsetting Atom
#2It's what kickstarted Electron which eventually gave us VSCode, Slack, and lots of HN comments about memory usage. It also had the sweetest default theme of any code editor. RIP.
Re: Sunsetting Atom
#3Translation: 'Extinguishing Atom Text Editor'.
Really expected and unsurprising.
Re: Sunsetting Atom
#4What recommendations do you all have for alternatives?
Re: Sunsetting Atom
#5What recommendations do you all have for alternatives?
I think the reason it's unused these days is because it's largely been replaced by vscode
Re: Sunsetting Atom
#6I think the writing was on the wall for a long time.
Since it is only happening in 6 months, I wonder if the community will try to transition/fork it.
Do you know if there is still enough interest?
Re: Sunsetting Atom
#7“Sunsetting” an open source project seems… unfitting? Hand it off to the community, look for new maintainers, donate it to the Apache Retirement Home for Veteran Projects, sure.
But saying that you’ve decided to “sunset” or “archive” it, telling users to plan for their migration, seems counter to the notion that open source software forms part of a commons - something that Github, of all companies, should understand.
Re: Sunsetting Atom
#8What recommendations do you all have for alternatives?
Visual Studio Code is the most obvious.
I actually forgot Atom existed. I move from it to VSC because Atom was just such a resource hog.
Re: Sunsetting Atom
#9What recommendations do you all have for alternatives?
VSCode seems to be the go-to for most.
Re: Sunsetting Atom
#10What recommendations do you all have for alternatives?
Sublime I guess. I made the switch awhile back because if just how much snappier it is, but it’s sad to see Atom go with all its nice add-ons…