Sunsetting Atom
11–20 of 880 posts
Re: Sunsetting Atom
#12What recommendations do you all have for alternatives?
vim -> Sublime -> Emacs -> VSCode -> Emacs
^^^^^ I am here.Re: Sunsetting Atom
#13What recommendations do you all have for alternatives?
Re: Sunsetting Atom
#14“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.
We should be counting down the days till they sunset VS Code to focus on VS Code "Pro".
Re: Sunsetting Atom
#15Re: Sunsetting Atom
#16Re: Sunsetting Atom
#17Re: Sunsetting Atom
#18What recommendations do you all have for alternatives?
Re: Sunsetting Atom
#19Re: Sunsetting Atom
#20What recommendations do you all have for alternatives?
But realistically? A significant majority of developers use Visual Studio Code; Atom is still only being used by absolute diehards. Visual Studio Code's complete supplantation of Atom (with which it competes for resources in the same organization) is why we're having this discussion.