markdown guide
 

I started out with Atom when I began coding, but now I use VS code. VS code is more developer oriented like the settings panel is in JSON! VS code also seems to be a tad bit faster, and that's what all the cool kids use!
(Mind F**k): VS code is made/managed by Microsoft, Atom is managed by Github. Github is bought by Microsoft ...

 

I was using Atom before; probably about 2 years ago, but there wasa bug that they allowed in their software that Microsoft's team addressed and that bug was looking my battery, so I switched and never looked back. I understand that bug is fixed now, but I'm no longer motivated to switch likei was when I was new.

 
 

I use Atom because Vim emulation in Atom (the highly-extensible vim-mode-plus package) far surpasses any Vim not just in VS Code, but in any other editor. I can literally everything that I can do in Vim in Atom, and in Atom it is even better with my custom additions.

As a Vim user (editing code VERY CONVENIENTLY AND FAST), VS Code just isn't there yet (and yes, I've explored the available plugins and features).

For example, in Atom, commands like :'<,'>s/old/new/g to find-replace in the whole buffer works, etc!

It's been a while since I've evaluated all the Vim-style possibilities in VS Code though. At this point in time, many of the features of my 1.5k line vimrc work in Atom and were easy to set up.

 

Little bit late, but you can use neovim with the vim extension, which will definitely solve your problem. I'm not sure so much about the vimrc, but honestly the stability, speed, and just better design of VScode was worth it for me to switch.

 

Sounds cool. I'd definitely like to give it another go. It's been a while since I've tried VS Code.

I definitely recommend it. It took a while for me to get used to it, but the speed benefits, better key combos, better/more consistent design, better language support and tooling (Typescript type annotations are absolutely amazing), and better command pallet made it worth it for me.

Yeah, the TypeScript support in particular is what interests me the most (especially because I also want to get into AssemblyScript (TypeScript for WebAssembly)), but at the time I was comparing Atom and VSCode, the Vim support in Atom far outweighed the better TS support in VS Code for me. I will definitely have to swing back around to see how they compare nowadays. I'm hoping vim support in VS Code is as configurable and flexible in Atom (in Atom I can script the vim-mode-plus plugin with practically all the same features as native Vim, it's the first vim-emulation of any editor that I ever actually liked compared to native Vim).

 

I have been using VSCode for years but I have to say, Atom has really caught up and I prefer its look and that it's simpler and most importantly that it's not pushing MS products like Azure.

 

With Microsoft buying GitHub, it would make sense to dump Atom support, focus exclusively on VSC and split the Atom team between those interested in Electron and those wanting to continue with VSC. I think Electron is just scratching the surface of what's possible and deserves more investment, which i believe could suit Microsoft strategically.

 

I tried to switch to VS Code, since most of my team has switched to it, but I went back to Atom. I'm going to ride it out with Atom until M$ inevitably kill it.

 

I started with atom. but now i use vs code for daily. my friends recomended vs code cause it has a good platform and many extension.

 

I used Atom but it had memory issue that time, Since then they have improved a lot but I switched to VS Code and never looked back!

 

Atom is lately just left in dust by VS Code... IMHO it feels super laggy. In addition VS Code easy support for all possible languages and existing plugins makes it just different league than Atom

 

I prefer to use Atom Git GUI interface for git stuff and vs-code for coding.

 
Classic DEV Post from Apr 24 '17

Compensation tips

Advice on compensation, seeking raises, and determining when to change jobs shared from my own experiences.

Hunter Drum profile image
On a mission to build simple versions, of complex things, and complex versions, of simple things