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

71–80 of 880 posts

Re: Sunsetting Atom

#71

Post by jacobmischka »

jonathaneunice wrote: post #27

I like Atom and use it occasionally. But I use VS Code day-in and day-out. The decision makes sense. If VS Code were not exceptionally good, Atom might have had more of an opportunity. But "yet another good option" is not enough to drive investment, sustain a community, and spin an ecosystem.

Atom predated VS Code and was the impetus for Electron, which VS Code uses. You may know this, but this comment makes it seem like they tried and didn't have an opportunity. They literally invented what the majority of new "desktop" apps uses to render UIs, they just couldn't compete with Microsoft (before they were bought out, after which of course Microsoft wasn't going to invest seriously in it).

Edit: Fixed typo (thanks torstenvl!).

Re: Sunsetting Atom

#72

Post by pjmlp »

mumblemumble wrote: post #60
jaywalk wrote: post #43

Earlier quoted context omitted.

VS Code Pro already exists. It's called Visual Studio.

Despite the name, they have basically nothing in common. They don't share a user interface, they don't share plugins, they don't share hotkeys. One of the main complaints many of the C# developers on my team have when they have to touch languages that aren't well supported by Visual Studio is that they don't know how to work VSCode.

They do share some plugins actually, that is why VS nowadays also gets a node instance running on the background.

And also why C++ workloads depend on .NET being available.

Re: Sunsetting Atom

#73

Post by wly_cdgr »

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

Re: Sunsetting Atom

#74

Post by chii »

wrycoder wrote: post #55
jaywalk wrote: post #21

Earlier quoted context omitted.

If the community actually cares enough, they can fork it and continue on with development.

Probably under a new name - I’d expect MS to be in control of the “Atom” trademark and branding, and they would stop further use.

if you attempt to sell, or commercially utilize the atom name in a fork of the project, i can see why microsoft would stop you.

Re: Sunsetting Atom

#75

Post by piefayth »

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.

Well, if you just want a custom VSCode theme, you can try Theme Studio for VSCode: https://themes.vscode.one/. Login/signup required, though. No affiliation.

Re: Sunsetting Atom

#76

Post by ollien »

melling wrote: post #36
ollien wrote: post #17

Earlier quoted context omitted.

and then vim again. It will come full circle :)

vim bindings in Emacs. :-)

I end up with vim bindings in VSCode at the present. It doesn't do everything but it does most things I want. There is neovim integration, but last time I tried it there were a bunch of glitchy things that didn't work right (I remember selection being buggy but I can't remember the specifics). Maybe I'll have to give it another whirl.

Re: Sunsetting Atom

#77

Post by colordrops »

joshstrange wrote: post #56

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…

Totally agree, if I'm gonna put effort into building my IDE it's gonna be vim or emacs. I use nvim most of the time and intellij on occasion for debugging.

Re: Sunsetting Atom

#78

Post by tinco »

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 market, and the community is much better off with only one of them.

Instead of letting it slowly bleed out and randomly catching stragglers with outdated marketing materials lingering on the web, they give it a swift death. Atom can go into the history books as an open source project that defined the industry for a decade.

Re: Sunsetting Atom

#80

Post by pantulis »

bitwize wrote: post #20
mproud wrote: post #4

What recommendations do you all have for alternatives?

Honestly? Emacs. Gonna be around for at least as long as RMS is still alive. I'd accept Vim as a runner-up; I'm conversant in it and can see where people might prefer it (though honestly, those people should probably enable evil-mode in emacs). 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…

I used to say that investing some time in becoming proficient with Emacs (the One True Editor!) or vim will deliver returns over a lifetime-spanning career. But Visual Studio Code has already joined them and it is a pretty sensible editor platform to learn.

Also totally subject for discussion: I suspect VS Code will see more innovation in years to come.

Post reply on HN