Translation: 'Extinguishing Atom Text Editor'. Really expected and unsurprising.
Sunsetting Atom
41–50 of 880 posts
Re: Sunsetting Atom
#42Re: Sunsetting Atom
#43“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.
GitHub is owned by Microsoft, the company that invented "Embrace, Extend, Extinguish". We should be counting down the days till they sunset VS Code to focus on VS Code "Pro".
Re: Sunsetting Atom
#44“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.
GitHub is owned by Microsoft, the company that invented "Embrace, Extend, Extinguish". We should be counting down the days till they sunset VS Code to focus on VS Code "Pro".
Re: Sunsetting Atom
#45I remember this being released and this was a concern at the time that the project would be abandoned. If I remember this it was mostly a concern as Github as a company should focus on their main product which is not an editor and that there are many existing editor that do it better. I suspect that what actually killed this is the acquisition of Github by Microsoft and the fact that Microsoft are pushing VSCode very…
Re: Sunsetting Atom
#46Earlier quoted context omitted.
GitHub is owned by Microsoft, the company that invented "Embrace, Extend, Extinguish". We should be counting down the days till they sunset VS Code to focus on VS Code "Pro".
When this inevitably happens to VSCode, I'm sure we'll all flock to Sublime Text in droves (or some hip new editor on the block). Contingency planning for this could be a small but wise time investment for dependent teams. VSCode could very well go the way of the Do... Docker.
Re: Sunsetting Atom
#47“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.
But winding down the project is still a major event, and I think that it is appropriate to call that sunsetting. The existing project organization will go away. The team will presumably dissolve, with any people being paid to work on it going on to other things. I've seen this happen enough times to know that it is, indeed, an end of sorts. "The community" is almost never large and organized enough to keep a project like this vital. At best, they can only slow its descent into obscurity.
Re: Sunsetting Atom
#48Earlier quoted context omitted.
GitHub is owned by Microsoft, the company that invented "Embrace, Extend, Extinguish". We should be counting down the days till they sunset VS Code to focus on VS Code "Pro".
When this inevitably happens to VSCode, I'm sure we'll all flock to Sublime Text in droves (or some hip new editor on the block). Contingency planning for this could be a small but wise time investment for dependent teams. VSCode could very well go the way of the Do... Docker.
Re: Sunsetting Atom
#49Re: Sunsetting Atom
#50What recommendations do you all have for alternatives?