Skip to content

Instantly share code, notes, and snippets.

@j-mes

j-mes/atom-vs-code.md

Created December 21, 2018 11:01
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save j-mes/efb5142f8ee14d7c909d9c37eadcf47c to your computer and use it in GitHub Desktop.
Save j-mes/efb5142f8ee14d7c909d9c37eadcf47c to your computer and use it in GitHub Desktop.
Download ZIP
Atom against VS Code
Raw
atom-vs-code.md

Atom against VS Code

This is an opinionated gist, so please do not take this as sacrosanct. I started using Atom in March 2014 to April 2016. From April 2016 to present it's VS Code. Before Atom, I was using Sublime, and this was for a long time with a cracked version 😬

Atom

Pros

  • Open Source
  • Uses Electron (HTML/CSS/JS)
  • Costs nothing
  • Pretty to look at
  • Easy to configure compared to Sublime
  • Healthy eco-system of plugins/themes
  • Teletype for Atom is awesome. You can do pair programming with different laptops/users

Cons

  • Can use a lot of system resources
  • Not great with Emmet
  • Add in a lot of plugins to improve core functionality which can contribute to Atom being slow/resource-hungry
  • Needs a lot of configuring to match your needs i.e. Emmet, and so on

VS Code

Pros

  • Open Source
  • Uses Electron (HTML/CSS/JS)
  • Costs nothing
  • Easy to configure (now, not before)
  • Healthy eco-system of extensions/themes
  • Can use keymaps from Sublime/Atom or other editors
  • Node.js orientated for debugging etc
  • Blazing fast and is light on system resources
  • IntelliSense
  • Emmet built in and works with IntelliSense
  • VS Live Share is fucking awesome - Pair programming in different locations not an issue

Cons

  • Can be confusing to use native VS Code shortcuts - It's easier to use Sublime in my use case

So there you go, this is why I go with VS Code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment