r/javascript • • Feb 06 '19

Visual Studio Code January 2019

https://code.visualstudio.com/updates/v1_31
342 Upvotes

119 comments sorted by

View all comments

156

u/[deleted] Feb 06 '19

[removed] — view removed comment

88

u/careseite [🐱😸].filter(😺 => 😺.ā¤ļøšŸˆ).map(😺=> 😺.šŸ¤— ? 😻 :😿) Feb 06 '19

VS Code is leaving Atom in the dust.

when I adopted VS Code last March it was alredy lightyears ahead of Atom by speed alone, not even talking about the ecosystem and the features...

39

u/pizzainacup Feb 06 '19

When I first started learning programming a bit over a year ago I had to switch from Atom to VSCode cause Atom ran terribly. Not a single flaw with VSCode for me so far.

6

u/[deleted] Feb 07 '19

I was using Atom for a while at my last job. I could sit and watch my battery percentage drop. It would absolutely destroy my laptop battery. It was so poor.

58

u/Baryn Feb 06 '19

Atom has been irrelevant for at least a couple years.

8

u/[deleted] Feb 07 '19

I still like it and use it 😊

5

u/SemiNormal Feb 07 '19

Not that there's anything wrong with that.

5

u/ChucklefuckBitch Feb 07 '19

Microsoft has made statements that there are no plans of abandoning Atom, and that work on it will continue like before.

9

u/goto-reddit Feb 07 '19

Yes, he said that in an AMA 8 month ago, it was the top question:

I’m Nat Friedman, future CEO of GitHub. AMA.

What plans does Microsoft have regarding GitHub's Atom text editor (which obviously overlaps in target user with VS Code)?

Ā 

Developers are really particular about their setup, and choosing an editor is one of the most personal decisions a developer makes. Languages change, jobs change, you often get a new computer or upgrade your OS, but you usually pick an editor and grow with it for years. The last thing I would want to do is take that decision away from Atom users.

Atom is a fantastic editor with a healthy community, adoring fans, excellent design, and a promising foray into real-time collaboration. At Microsoft, we already use every editor from Atom to VS Code to Sublime to Vim, and we want developers to use any editor they prefer with GitHub.

So we will continue to develop and support both Atom and VS Code going forward.

-3

u/[deleted] Feb 07 '19

Talk is cheap (c).

4

u/snyper7 Feb 07 '19

A coworker of mine was lauding atom a few years ago, so I gave it a try. My first impression was that it was incredibly slow. I went back to Code pretty quickly. I'm pretty sure he uses Code exclusively now too.

Interesting thing - many portable applications, including VSCode and Atom, run in an environment called "Electron." Electron was developed as the runtime environment for Atom, or the "Atom shell." Atom shell - Electron.

1

u/bob51zhang Feb 07 '19

That's a really cool naming scheme, is there such thing as proton?

1

u/snyper7 Feb 07 '19

Not that I'm aware of, but that would definitely be a cool name for an OSS project.

12

u/seiyria Feb 06 '19

Die-hards will use it, it will stop being supported, vscode will take over. It will be the new vim.

3

u/rohmish Feb 07 '19

I have my atom install modded to hell with what I want just as atom started to become "irrelevant". Hard to move over but I'm working on it

5

u/keef_hernandez Feb 07 '19

Vim is supported.

13

u/CaptainLepidus Feb 07 '19

They mean: VS Code will be the new Vim, in terms of dominance in this space.

6

u/[deleted] Feb 07 '19

So, Atom just die slowly.

7

u/Mittalmailbox Feb 07 '19

Number of commits does not tell full story

4

u/mournful-tits Feb 07 '19

It does show level of interest and commitment to a project. You could argue commits don't mean much for a mature project with relatively few bugs and a feature set that has an answer to everything (albeit some less than ideal)... But that isn't Atom.

2

u/devperez Feb 07 '19

Eventually they will likely stop developing it. But when MS Github, they promised to keep it around for now at least.