Best Text Editor? Atom vs Sublime vs Visual Studio Code vs Vim

Published Sep 28, 2016Last updated Jan 18, 2017
Best Text Editor? Atom vs Sublime vs Visual Studio Code vs Vim

With so many programming text editors out there today, the seemingly simple task of choosing one suddenly becomes daunting and overwhelming.

While a straightforward answer to the "what is the best text editor for developers?" question doesn't exist, in this post, I will share with you a side by side comparison between four of most popular ones out there: **Atom, Sublime, Visual Studio Code, and Vim. **

After reading the list of pros and cons, I hope you will have enough information to make a choice that best fits your needs.

Disclaimer: As with any comparison, some of these views are subjective and are mostly based on my personal preferences. I'm someone who writes for the web (JS, CSS, HTML, etc.) using Sublime for Mac, so my perspective is a bit skewed towards what I'm used to. That said, I've tried to be as objective as possible.


text editor

  • Url:
  • Cost: Free (MIT Licence)
  • Developer: GitHub
  • Platforms: OSX, Windows, Linux

Atom is described as:

A hackable text editor for the 21st Century

Atom is a relative newcomer to the world of text editors but it's gained huge momentum since it was first released in 2014. Let's start by reviewing its main features:


text editor

Ability to add additional features to an edit is very important, and this is an area that Atom shines at. The package manager is installed by default and to make things even better, all packages are hosted on Github.

At the time of writing, they had a whopping 6,452 packages and themes available! Packages are so fundamental to Atom, that core features like Tree View and Settings View are simply pre-installed packages.

Editing and Workflow

In general, everything in Atom is rather smooth. Biggest pain point? Figuring out which additional packages need to be installed when starting from scratch.

For example, I like minimap to help me visually skip to parts of a file. I also needed to set up some autocompletion using Autocomplete +. I'm someone who often works on a couple of files simultaneously so the ability to set up split pane editing is a must. It's a feature Atom supports nicely.

enter image description here

Another nice feature of Atom that I've found lacking in Sublime is the drag/drop file/folder support in the tree view. I'm so used to not having it in Sublime that being able to shift things around is a real treat!

Finally, the git integration is great... it is made by GitHub after all!


Ability to customize an editor to match your development flow and style is essential. Personally, I always need to enable things like "trim whitespaces on save", "save on lost focus of file", both of which are easy to set up and override in Atom.

Atom has a great doc page on how to even override the styles (Atom's written in pure HTML/CSS on top of Chromium) -

text editor

Overall, I love how configurable Atom is—ability to override settings on a per-file type basis is great! For example, different indentation for JS vs CSS vs HTML is very simple with Atom.


If there's one bone to pick with Atom, it's that at times, it feels slow. Sometimes, opening a file or switching between tabs has enough of a lag to feel painful (especially when you're in full swing development action). When I tried Atom when it was first released, performance was a problem. It has certainly gotten better since, but the frustration is still there.


Atom is a great tool, especially for those who want to customize their editor easily, and beyond what others provide. As a web developer, the freedom to tweak, add, and extend your editor gives an incredible feeling of power. I also love its docs. The Atom Flight Manual provides a great starting point for new users.

The greatest downside for me would still be the performance issues, but for a free editor, Atom shines brightly!


text editor

  • Url:
  • Cost: $70 license fee with free trial
  • Developer: Jon Skinner former Google Engineer
  • Platforms: OSX, Windows, Linux

Sublime was released back in 2007, so it's had almost a decade to mature. According to Stackoverflow's 2016 developer survey it's the 3rd most popular Development Environment.

V3 Beta is its latest version and while it's been in beta for a long time now, don't let that concern you. The product is actually very stable.


Any Sublime user will tell you the first package they install is Sublime Package Control plugin. I think we all secretly hope that Sublime 3 will add this by default, but for now, you simply have to go to the installation page on their website and copy some incomprehensible Python and... Presto! You can now install any package easily from within Sublime.

text editor

Like Atom, Sublime has a lot of packages and themes! For me the essentials are:

  • SideBarEnhancements: without this, renaming/moving/duplicating files is not supported.
  • SublimeLinter: To add linters for different languages
  • GitGutter - Shows git status on the left side next to line numbers.

There's plenty more to choose from, too. Overall, Sublime's package support is very good, it's just a shame that you have to jump through that one hoop at the beginning to even get started with it.

Editing and Workflow

For me the use of projects is critical when working in Sublime - it helps me stay focussed on the relevant files for what I need. Being able to search for a file and across files is fast and easy. I've often had to perform searches across hundreds of files to find a snippet of code and Sublime's speed has never let me down.

As with Atom—the real power comes once you have some key plugins installed. Getting the right syntax highlighting, JSON formatters, linters, etc takes some time, but once they're installed and set up, they don't need to be touched again.

One downside I've found is there's no decent Git plugin that lets me do nice diffs and stage changes. I only really trust using SourceTree for that. I'm sure others will be able to correct me if there is a decent plugin that can help.


Again, Sublime is very much like Atom. The power to control aspects such as "save on lost focus", "trim whitespace" and more is available. The configuration files are simple JSON and there's a whole host of hidden settings waiting for you to play with.


Here's where Sublime outperforms Atom—opening, closing, searching, etc is very smooth and fast. The only issue I've ever faced with performance is from badly performing plugins—but even then you'll get a warning message when a plugin seems to be taking too long.


As I mentioned at the start, I'm a long time Sublime user so my opinions here are likely to be slightly biased, but in general, Sublime is a flexible and fast editor. There's a reason it still makes the top 3 Development Environment in 2016.

Visual Studio Code

text editor

Visual Studio Code (VSCode) is a relative newcomer to the world of text editors. It was only released last year (April 2015), but it has already been picking up a lot of traction. Microsoft has done a great job of creating a powerful and flexible cross-platform editor that's piquing a lot of interest from developers.


As with our other editors, VSCode has a nice plugin (extensions) ecosystem. The extension management is built-in, and there's already several thousands available! As with Atom, some come installed by default.

You'll need to spend some time picking out plugins that are best for your workflow. One of my favorite (and what makes me excited about VSCode) is Debugger for Chrome. It allows you to set breakpoints and debug JS from within VSCode.

text editor

The same can also be done with Node.js—setting breakpoints in VSCode and stepping through while the node process runs in a terminal.

Editing and Workflow

Although VSCode is built in a similar fashion to Atom, using Electron, Node, and HTML/CSS, it is actually much faster without any real lags.

I spent a week using the editor, and in general, I was pretty content. It had a very familiar feel to Sublime and Atom. The debugging feature mentioned above was a treat. I also set up some of the IntelliSense typeahead completion which (although painful to configure initially) started to show its benefits in a day or so. I could already whizz through typing out a function name without having to remember the arguments (or their types for that matter).

As an added bonus, the Git integration is very convenient. Not as powerful as what I get using SourceTree, but for common operations like commits and diffs, it proved to be perfect and sped up my development time.


Like the previous two editors, the expected customization features are there—all the necessary wrapping, indenting, theming, language tweaks, etc.


As mentioned before, although VSCode (like Atom) is built on Node.js, Electron, HTML, and CSS, it definitely feels fast (unlike Atom). I didn't experience any lags when opening/changing files. Searching was also fast. I believe one of the differences between Atom and VSCode is that the UI Editor is built on Monaco (from Visual Studio Online), which might be the explanation for the performance difference. In any case, the performance is definitely on par with Sublime.


Overall I was very impressed with VSCode, to the point that I've considered moving to it more permanently. I'm still yet to take that step to fully dive in, but I think it would be a nice holiday project to configure it to meet similar standards I am used to in Sublime. After that, I think I really could stick with it for longer. The Git integration and in-editor debugger are great features that I've struggled with in Sublime but worked almost immediately in VSCode.


text editor

  • Url:
  • Cost: Free GPL compatible licence
  • Developer: Bram Moolenaar
  • Platforms: OSX, Windows, Linux

I feel like all developers should at some point go through a "rites of passage" and use Vi or Vim for a project. Ability to edit or view a file on a remote server through a terminal is a hugely productive and important task. I've seen many developers jump through all sorts of hoops using SFTP, or curl, and re-uploading files.

However, I also recognize that the sheer mention of Vim brings shivers to some, and even righteous indignation to others. Had I omitted it, I would fear a severe smackdown from the Vim power users 😉 In all honesty for those who have spent the time to master it, it is an incredibly productive environment!


At over 14,000 packages, Vim has one for everything! Tree explorers, syntax highlighters, theming, Git integration, etc. It's all there, in multiple versions. Vim is incredibly flexible and powerful. However as with all other editors mentioned above, knowing the best plugins to install requires some insider knowledge and recommendations.

Personally, I've found going off the most popular plugins on as a starting point.

Editing and Workflow

Firstly, for those not familiar with Vim, it is essentially a command line text editor. Therefore it's not some app you double click and use a mouse to move around in. The control of opening, closing, editing, saving is all keyboard shortcuts.

text editor

When I was in college, we were forced to work only in Vi for an entire module. Once you're forced to do something like that, the common keyboard commands start to become second nature. If you really want to become a Vim user, it takes real commitment, but I promise you will feel like an absolute genius by the end of it!

In all honesty, the reason I find working in Vim less efficient is because I don't know enough of the keyboard shortcuts. I can edit single files, searching, replacing, etc. with ease, but when working across multiple files, I start to lose track. So for me, Vim is a little too much.


Vim is amazingly customizable. If you Google search for .vimrc you'll find a lot of examples of preconfigured Vim configuration files. In short, anything is pretty much possible in Vim.


The only blocker to performance in Vim is the user... in other words you! It's as raw and as fast as it could be, but the performance is how quickly you can type your commands and move around! If you're a Vim power user it is blazingly fast!


Vim is as raw of an editor as you can get. It can be an incredibly fast, efficient development environment if you can have the patience to learn the commands. There's a great online game which helps to teach the basic commands, like moving around files using h, j, k and l keys.

Final Verdict

All of the above editors have their pros and cons. Personally, I'd say that in your developer's career, you should give each one of them a shot for at least a week to see for yourself what works and what does not work for you. I hope that summarizing those four most popular text editors will make for a good starting point when considering making an editor change.

What did we miss out? And what's your favorite editor? Let us know in the comments below.

Other tutorials you might be interested in

Discover and read more posts from Matt Goldspink
get started
Enjoy this post?

Leave a like and comment for Matt

Maksym Lanovyi
6 days ago

I encourage you to try Jetbrains IDEs. They’re really awesome.

a month ago

As a developer for over 17 years, there’s one thing first and foremost I expect from my text editors, and that’s performance that is instantaneous. Anything less is completely unacceptable. That’s why I choose Sublime Text over Atom & VS Code all the way. I also use VIM too when needed. You have IDE’s for large applications, but for text editors they have one job - to edit text. Any bells and whistles are fantastic, but it shouldn’t be at the cost of performance. You are never going to get the same performance using nodejs as you are with proper native compiled software. This really is a case of hipster technology for the sake of it. I’ll stick with the performance all the way. I don’t know how people can overlook this.

Matt Goldspink
a month ago

I’ll leave my 2cents since I wrote this one ;)

Gavin you’re right performance is key. However there’s a difference between raw numbers based performance and the ability to perform tasks quickly and efficiently.

The slowest part of VS Code for me is start up time, but not to the point that it breaks my flow. We’re talking around 1 second to open the app. Once it’s open it’s fast, even when changing projects. After that I’ve never once had it be slow, hang or anything else that ruins my workflow. The best editors for me are always the one that let you achieve your task as quickly as possible, whether that’s by providing keyboard shortcuts or tooling.

I’d also say that a “text editor” may just be for editing text, but editing text involves a lot more than simply typing and deleting text. You need search, replace, if the text file has a mime-type it needs to show syntax highlighting, opening files should be fast and simple, etc, etc. Other things like Git integration are debatable as whether they should be in a text editor or not, but given that I use a “text editor” for software development it’s a useful feature.

Having come from Sublime Text and moved to VS Code I can say that I code faster in VS Code than I did with Sublime Text. The shortcuts and tooling were just better suited to my workflow and projects.

This really is a case of hipster technology for the sake of it.

No Gavin - this is a post about Text Editors. The language they’re written in is one aspect of this. The most important thing is how well they help you do you’re job. If you’re averse to Node.js then that’s fine, but if you can look past the technology used to how well something enables you to achieve a job then you may have a different perspective. Rejecting something off the bat because it’s “not native” is not helpful in my opinion. It could be that the projects and files you work on need a lower level editor to handle them, thats fine.

Manuel Gonzalez
a day ago

As developer for over 20 years, nothing beats Edit in MS-DOS. Just kidding! I prefer Notepad++ when diddling. When serious I prefer VSCode. It just is.

a month ago

Even I have been using vim for 2+ years, I keep being surprised by some new efficient plugins.
Thanks a lot for your .

Show more replies