When comparing Emacs vs Visual Studio Code, the Slant community recommends Visual Studio Code for most people. In the question“What are the best programming text editors?” Visual Studio Code is ranked 3rd while Emacs is ranked 9th. The most important reason people chose Visual Studio Code is:
Visual Studio Code comes fairly complete out of the box, but there are many plug-ins available to extend its functionality.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Keyboard-focused, mouse-free editing
Emacs can be controlled entirely with the keyboard. While true, I often find the mouse and menus handy for those lesser-used commands. An aide-memoir.
Pro Total customizability
Customizations can be made to a wide range of Emacs' functions through a Lisp dialect (Emacs Lisp). A robust list of existing Lisp extensions include the practical (git integration, syntax highlighting, etc) to the utilitarian (calculators, calendars) to the sublime (chess, Eliza).
Pro It's also an IDE
You can debug, compile, manage files, integrate with version control systems, etc. All through the various plugins that can be installed.
Pro Free
Licensed under GNU GPL.
Pro Self documenting
Emacs has extensive help support built-in as well as a tutorial accessed with C-h t.
Pro Works in terminal or as a GUI application
You can use Emacs' command line interface or graphical user interface.
Pro Great documentation
With 30+ years of use the Emacs documentation is very thorough. There are also a lot of tutorials and guides written by third parties.
Pro Ubiquity
Fully compliant GNU-emacs is available on many platforms, and they all understand .emacs configuration files.
Pro Lisp customizations
With lisp customization, any behavior of Emacs can be changed. Update with pre-release patch can be also applied without recompiling the whole Emacs.
Pro dabbrev-expand (Alt-/)
Dynamic word completion.
Pro Provides org-mode
Advanced planning and publication which can start as a simple list.
Pro Mini buffer
You can pass complicated arguments in the mini buffer.
Pro Enormous range of functionalities (way beyond simple "text editing")
Through its programmability, a very broad range of functionalities can be integrated in emacs, turning it even into a "single point of contact" with the underlying operating system.
Pro Rectangular cut and paste
Emacs can select rectangularly.

Pro Vi keybindings through Evil mode
Evil mode emulates vim behaviors within Emacs. It enables Vi users to move inside the Emacs universe.
Pro Has been widely used for a long time
The first verion of Emacs was written in 1974 and GNU Emacs in 1984.
Pro Visual selection and text objects with Evil
Evil is an extensible vi layer for Emacs. It provides Vim features like Visual selection and text objects.
Pro Support multi-line editing, multiple frame, powerful paren, crazy jumping style
Review the "Emacs Rocks" video.
Pro Cross-platform
Works on Linux, Windows, Macintosh, BSD, and others.
Pro Integrates planning in your development process
You can jump straight from your org-mode files to programming tasks - and back - and build a seamless workflow.
Pro Helm plugin adds even more power to Emacs
Powerful commands, search, and more with the Helm plugin.
Pro Versatile
Emacs is great for everything.
Pro GTK+ widgets support
Since version 25 you can run GTK widgets inside Emacs buffers. One of these is the WebKitGTK+, which allows the user to run a full-featured web browser inside Emacs with JavaScript and CSS support among other things.
Pro Excelent tutorial to get you started
The tutorial you are presented with at startup shows you exactly what you need to get started and teaches you how to use the built-in help yourself later.
Pro Interactive Shells
Emacs has a number of shell variants: ansi-term, shell, and eshell.
Pro Gnus
Managing several large mailing lists has never been easier using Gnus. The threading commands and the various ways of scoring articles means that I never miss important messages/authors, etc. A joy to use.
Pro eshell is cross platform
You can use the underlying operating system shell as a terminal emulation in an Emacs buffer. Don't like the default shell for your configuration? You can change it to your liking.
Pro Excellent Lisp editing support
Built-in packages make editing Lisp source code feel natural.
Pro use-package and org-mode
Missing some neural package that predicts actions
Maybe in the next release ...
Pro Extendable through plug-ins
Visual Studio Code comes fairly complete out of the box, but there are many plug-ins available to extend its functionality.
Pro TypeScript integration
There is very solid TypeScript integration in Visual Studio Code. Both are developed by Microsoft and VSC itself is written in TypeScript.
Pro Embedded Git control
Visual Studio Code has integrated Git control, guaranteeing speed, data integrity, and support for distributed, non-linear workflows.
Pro JavaScript IntelliSense support
JavaScript IntelliSense allows Visual Studio Code to provide you with useful hints and auto-completion features while you code.
Pro Integrated debugging
VSC includes debugging tools for Node.js, TypeScript, and JavaScript.
Pro Ready to use out of the box
You don't need to configure and add plugins before being productive. However, you can add plugins if needed but for the basics you're well covered.
Pro Integrated terminal
There's no need to press alt+tab to go to a terminal: it is directly integrated into the editor. Shift+~
is a handy hotkey to toggle the integrated terminal.
Pro Great performance
For a 'wrapped' web-based application, Visual Studio Code performs very well.
Pro Updated frequently
There's a new release of Visual Studio Code every month. If you are one of the insiders then releases are daily.
Pro Extensions (aka plugins) are written in JavaScript
Extensions are written in either Typescript or JavaScript.
Pro Integrated task runners
Task runners display lists of available tasks and performing these tasks is as simple as a click of the mouse.
Pro ESLint integration
ESLint integrates great. You can define your rules trough .eslintrc.* as usual and vs code will autofix your code on save. So your code is always in style.
Pro Active development
It's really nice to see how the code editor evolves. Every month there is a new version with great communication of new features and changes.
Pro Libre/open source
Released under the MIT License.
Pro Custom snippets support
Snippets are templates that will insert text for you and adapt it to their context, and in VSC they are highly customizable.
Pro Fast and powerful
VS-Code has the speed of Sublime and the power of WebStorm. Perhaps this is the best software that Microsoft has ever created.
Pro Huge community behind it
The ease of getting assistance and finding tutorials is increasing as the community grows.
Pro It has gotten really good
All it takes is one stop for all the features many people need.
Pro Python support
Excellent Python plugin, originally created by Don Jayamanne, now hired by Microsoft to extend and maintain the extension.
Pro JS typechecking
It leverages TypeScript compiler functionality to statically type check JS (type inference, JSDoc types) with "javascript.implicitProjectConfig.checkJs": true
option.
Pro Good support for new Emmet syntax
Pro High fidelity C# plugin
The Omnisharp plugin is very powerful providing full sln, csproj, and project.json support.
Pro Support RTL languages
It supports pretty web rtl languages like arabic languages when most of other editors don't support it.
Pro Inline definition picking and usages finding
These features allow you to have a glance at code without opening it as a whole in a separate tab. Moreover, editing is allowed.
Cons
Con Learning curve is long
While it's better than it used to be, with most functions being possible through the menu, Emacs is still quite a bit different from your standard editor. You'll need to learn new keyboard shortcuts.
Con Sometimes the extensibility can distract you from your actual work
If I ever want to lose half a day, I'll start by tweaking my .spacemacs config file.
Con Keyboard combinations can be confusing for new users
For example, for navigation it uses the b, n, p, l keys. Which for some people may seem strange in the begging. However they can be changed easily.
Con Documentation is not beginner-friendly
Although lots of good built-in documentation _exists_, I have after four years of Emacs as my primary editor not figured out how to actually make use of it, and rely completely on Google / StackOverflow for help.
Con Hard customization
For customization, you need to learn Lisp
Con A lot of jokes in this serious software
Con Using Emacs on a new machine without your .emacs file
Con The autocomplete and code check is not as powerful as the one on WebStorm
Sometimes it doesn't tell you if you made a typo in a method name or if a method is not used and several other important features.
Con Embedded Git isn't powerful enough
You can do nothing but to track changes, stage them and commit. No history, visualization, rebasing or cherry-picking – these things are left to git console or external git client.
Con Project search limits results
Because file search is so slow your results are limited in order to simulate a faster search.
Con Very bad auto import
Con Generalized
VS Code is a general code/scripting IDE built to be lightweight and for people familiar with their language of choice, not directly comparable to Visual Studio in power or scope.
Con Memory hog
Allegedly, VS Code is "lightweight". Yet, running multiple instances of it at once, you may get many "out of memory" messages from Windows despite 16 GB RAM. (While of course also running other things. The point is the comparison with some other IDEs/editors where running them alongside the same number of other applications doesn't cause Windows to run out of memory)
Con Poor error fix suggestions
Error detection and suggestions/fixes are poor compared to IntelliJ platforms
Con A "me too" offering from MS, far behind other well established editors that it attempts to clone
Other IDEs specific to a language often offer better tools for deep programming.
Con Slow launch time
Than it's competitors, e.g. Sublime Text.
Con Emmet plugin often fails on even simple p tags
Con Have no good default js style analyzer
In WebStorm there is analyzer that checks for warnings and highlight this in yellow, here you cannot find or add it even with plugins. It is possible to have it as errors with linter but while you are actively changing file that's not very nice.
Con File search is extremely slow
It's absolutely not possible to use this tool with big projects given how long it takes to search for files.
Con .sass linting is terrible
Con Is not an IDE, is a text editor
Built By the Slant team
Lustre recommends the best products at their lowest prices – right on Amazon.