Live data from Hacker News

Sunsetting Atom

github.blog

81–90 of 880 posts

Re: Sunsetting Atom

#81

Earlier quoted context omitted.

I’m not sure the term has ever been applied to Microsoft’s own products…

Atom was developed before the acquisition. Which brings us to the second proud tradition of the tech titans, acquiring companies to end the products the acquirer doesn't like.

Well yeah, if you have two very similar products (editors/IDEs based on web technology), one of them much more successful than the other, putting a lot of effort into the less-used product sounds a bit hard to justify...

Re: Sunsetting Atom

#83

I know a lot of people love vscode but are there any people who have tried something like IDEA/WebStorm/PHPStorm/etc that then went back to vscode? I had to help a developer setup deploys to a dev server from vscode the other day and I wanted to pull my hair out. I'll admit it's at least in part due to not using vscode myself but I was a heavy Sublime Text user which is very similar to vscode when it comes to how you…

https://code.visualstudio.com/docs/remote/remote-overview

far better and faster than sftp

Re: Sunsetting Atom

#84

Earlier quoted context omitted.

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.

Why would this happen to VsCode? VSCode is a proprietary form of Atom is not? It’s hugely successful Microsoft would never do such a thing.

Sort of?

They maintain a trademark on the name Visual Studio Code and some other bits. And it is maintained by a Microsoft team.

But the code itself is MIT licensed. You can build it yourself. I have. There are one or two forks of it out there.

Re: Sunsetting Atom

#85

Atom has been dead for years, this is just the state funeral. The situation now is: * Sublime for the Williamsburg corpo-hipsters * emacs and vim for the wizards and furries * VSCode for all the normies who just want to get on with doing their job and don't feel a need to express their identity or politics through choice of editor * WebStorm for the chads with the monster rigs to run it

This makes me feel conflicted.

Re: Sunsetting Atom

#86
post #40

“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.

I agree in principle, but I find it hard to imagine that there's enough interest to find someone who is willing to maintain the software and the package registry. Speaking of packages - of the six featured packages I get offered on atom.io, only one had a release in the last two years, and half have been unchanged for half a decade. Atom's already dead.

A lack of releases could mean dead, but it could also mean finished. As in, complete: not in need of more features, and having no bugs of sufficient severity to bother fixing.

Finished is a state more software should aspire to reach. Sadly, with the advent of connectivity in everything, it's getting rare for even firmware to be finished.

Re: Sunsetting Atom

#87

Earlier quoted context omitted.

Atom was developed before the acquisition. Which brings us to the second proud tradition of the tech titans, acquiring companies to end the products the acquirer doesn't like.

Does Microsoft not "like" Atom, or has its market share dwindled to the point that it is no longer worth maintaining?

Probably a bit of both if I was to hazard a guess. MS has VS Code, which is definitely the elephant in the room as far as go to IDEs in the environments I’ve been in lately. So right now they’re spending engineering time on both VS Code and Atom, so they may as well focus their resources on the more popular one.

Re: Sunsetting Atom

#88
This makes me sad as I very much prefer the atom approach to the git and github panels than the vscode approach. vscode is much faster for typescript development though.

Re: Sunsetting Atom

#89
post #2

It'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.

Does anyone remember brackets? I cant remember if brackets or atom came first but I remember switching from sublime to brackets to atom. Good times, I heard DHH is still using TextMate.

I do, it was quite cool! What stuck most with me is the CSS color picker.

Re: Sunsetting Atom

#90

I 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…

What other editors are better and could be recommended? I guess I'm replacing Atom today

Sublime Text gets my vote. Pretty hard to go back to anything else after using it.

It’s not free, but if you’re really strapped for cash you can use it like most people use Winrar, at least until the guilt overcomes you.

Post reply on HN