Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sunsetting Atom

github.blog

Post reply on HN
Print view View original

191–200 of 880 posts

Re: Sunsetting Atom

#191

Post by IncRnd »

tediousdemise wrote: post #37
civilized wrote: post #14

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

> Contingency planning for this could be a small but wise time investment for dependent teams.

I doubt that switching an editor requires a disaster-recovery plan.

Re: Sunsetting Atom

#192

Post by andrew_ »

Nooooooo. I so much prefer Atom over VSCode. I've read the spin, but this smells like Microsoft finally doing what we all predicted - killing off the competing product.

Re: Sunsetting Atom

#193

Post by MikePlacid »

tristor wrote: post #106
wly_cdgr wrote: post #73

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

* Textmate & BBEdit for people who were using Macs for development before they took over the tech industry.

I’ve “just” (as in: a couple of years ago) switched from BBEdit to Atom for my Python development, and now this.

Re: Sunsetting Atom

#194

Post by frostwarrior »

mumblemumble wrote: post #47
Doctor_Fegg wrote: post #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.

The code isn't being sunsetted, and anyone who wants to take it and keep working on it is free to do so. 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 i…

I agree.

Correct me if I'm wrong, but most projects started by some form of organization end up being dead after handing them off to the community. That is, unless they make their code from the ground up to be as most readable and modular as possible.

I remember many projects made by Sun Microsystems that just died when Oracle took over, even if the code is still there.

Re: Sunsetting Atom

#195

Post by ghshephard »

corrral wrote: post #61
philliphaydon wrote: post #24

Earlier quoted context omitted.

I like brackets but always ends up in VSCode due to extensions.

It's a very dumb reason to stick with an editor, but I have trouble going back to Sublime after VSCode despite preferring most things about Sublime, because I always forget how to manage packages using Sublime's command prompt and have to screw around with it for a while each time, while VSCode has a GUI for that so the memorization required is zero, and can easily browse available packages without bouncing out to a…

Ctl-Shift-P is used in VSCode as well as Sublime. And then, "Install Package"

Or through the Gui - "Preferences --> Package Control"

Re: Sunsetting Atom

#196

Post by akagusu »

mproud wrote: post #4

What recommendations do you all have for alternatives?

Just buy a license for Sublime Text or any intelliJ IDE.

If you use your text editor professionally, they more than worth the investment.

And if you want to build a text editor for your own needs, Emacs and Neovim are your friends.

Re: Sunsetting Atom

#197

Post by reactspa »

wly_cdgr wrote: post #73

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

Anyone else use Notepad++ ?

Why not?

Re: Sunsetting Atom

#198

Post by deeptote »

tlhunter wrote: post #104

Even though Atom was much "lighter" than VS Code in terms of UI, VS Code had so much more development resources thrown at it that it was ultimately much speedier than Atom. IIRC, even Brackets was faster. I see people complaining about the death of Atom, but in the past few years there just hasn't been a use case where Atom was the best choice.

Seriously, who actually uses Atom anymore? Before VSCode was a thing, I used it but then I got into Vim, Neovim, and now VSCode with the Vim plugin.

Re: Sunsetting Atom

#199

Post by whiskey14 »

rgoulter wrote: post #155
Atreiden wrote: post #38

Called this ~4 years ago when they were acquired by M$. But it's still really sad to see. I use it because it was trivial to CSS style it to match my Desktop. It's comfortable to me in a way that other editors thus far have not been. Are there other editors with this level of customizability? I know VSCode and Sublime support theming but from what I can tell it involves installing pre-packaged themes.

If level of customizability is your main metric: Emacs can go from this: https://emacshints.files.wordpress.com/2013/09/spash1.png to this: https://github.com/rougier/nano-emacs

+1 for nano-emacs

Re: Sunsetting Atom

#200

Post by wiseowise »

civilized wrote: post #29
red_phone wrote: post #22

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.

> Which brings us to the second proud tradition of the tech titans, acquiring companies to end the products the acquirer doesn't like.

Atom is inferior in every aspect to Visual Studio Code. Atom was on life support for too long.

Post reply on HN