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

121–130 of 880 posts

Re: Sunsetting Atom

#121

Post by SketchySeaBeast »

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.

I don't know why Microsoft would do that - VSCode is HUGELY popular and at the forefront of Microsoft "I'm cool now guys!" 'open-source' movement.

Re: Sunsetting Atom

#122

Post by bogwog »

keewee7 wrote: post #79

Really begs the question what Visual Studio Code did right and what Atom did wrong.

I didn’t use Atom much, but I think it’s obvious that the primary reason it died was because Microsoft decided to make their own competing editor, and then bought the parent company of Atom. It wasn’t exactly the most popular editor at the time, but it did still have some users.

Reminds me of how Adobe killed off FreeHand (the only competitor to Illustrator at the time) by buying the parent company and then halting development.

Of course, Microsoft likely gave zero shits about Atom as a competitive threat since it was effectively dead at the time anyways, but I still think it’s interesting to see the similarities to the Adobe situation.

Re: Sunsetting Atom

#123

Post by adregan »

ilrwbwrkhv wrote: post #92
mproud wrote: post #4

What recommendations do you all have for alternatives?

I don't know why anyone would ever move away from Sublime Text in the first place.

Sublime Text came pretty close to dying during the Sublime Text 2 years. I recall development slowed down substantially (it was a solo dev, IIRC), and it being pretty surprising when Sublime Text 3 came out.

Re: Sunsetting Atom

#124

Post by burlesona »

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

"VSCode for all the normies" ... feels weird. Maybe it's true. But I feel like VSCode rose 1:1 with Typescript, and I kind of resent it because I associate it with script kiddies around me cargo-culting React in places it isn't needed and writing thousands of lines of overcomplicated javascript to "manage state" on pages that don't even need to have any.

It's also noticeably slower than Sublime, which makes switching hard.

But "Williamsburg corpo-hipster" feels off the mark. To me Sublime aligns more around the "JS minimalist" camp, which overlaps a lot with the "bootstrapped and profitable" crowd.

Re: Sunsetting Atom

#125

Post by omoikane »

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

I disagree with these labels, I would say the choice of editor is more religion than politics.

Re: Sunsetting Atom

#126

Post by jamil7 »

skohan wrote: post #118
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

So MS owns the default place where code is hosted, and the default tool people use to edit code. Neat.

Cool and normal.

Re: Sunsetting Atom

#127

Post by [deleted] »

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

[deleted]

Re: Sunsetting Atom

#128

Post by bitwize »

philwelch wrote: post #108
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

> emacs and vim for the wizards and furries …respectively? TIL I’m a furry.

Now all you need is a nice comfy pair of programming socks.

Re: Sunsetting Atom

#129

Post by blackoil »

tinco wrote: post #78
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.

No it's perfectly reasonable. That open source software forms some part of a commons is not really a thing in practice. Open source software is ran by maintainers, those maintainers own the projects, and they do with the software what they deem fit. And even if it were, VSCode is basically a rewrite of Atom that reuses a big chunk of the original codebase, they're the same sort of project serving the same sort of mar…

> VSCode is basically a rewrite of Atom that reuses a big chunk of the original codebase

It isn't true anymore then saying Slack is rewrite of Atom. While it is using electron, editor and IDE aren't from Atom.

Re: Sunsetting Atom

#130

Post by gcau »

I still use Atom purely for its simple easy git UI (while coding in VSCode). VSCodes git UI, and all others I've seen, are a disaster in comparison. I want a simple, easy UI - in atom its exactly that. If I need more I'll just type it in the CLI. I wish there was something else I could use that's like this.
Post reply on HN