Vim vs WebStorm

When compared to modern graphical editors like Atom and Brackets (which have underlying HTML5 engines, browsers, Node, etc.), Vim uses a sliver of the system's memory and it loads instantly, all the while delivering the same features. Vim is also faster than Emacs.

Vim is open-source, GPL-compatible charityware.

Unlike other editors such as Sublime Text, Vim is a command line editor and hence can be used in remote development environments like Chromebooks via SSH.

Vi/vim exists on almost all Unix-like platforms. It's the de-facto Unix editor and is easily installed on Windows. All you need to make it work is a text-based connection, so it works well for remote machines with slow connections, or when you're too lazy to set up a VNC/Remote Desktop connection.

There's no need to reach for the mouse or the Ctrl/Alt buttons again. Everything is a mere key press or two away with almost 200 functions specifically for text editing. Vim does support the mouse, but it's designed so you don't have to use it for greater efficiency.
Versions of Vim, like gVim or MacVim, still allow you to use the mouse and familiar platform shortcuts. That can help ease the learning curve and you'll probably find you won't want to (or need to) use the mouse after a while.

Vim's keyset is mainly restricted to the alphanumeric keys and the escape key. This is an enduring relic of its teletype heritage, but has the effect of making my ost of Vim's functionality accessible without frequent awkward finger reaches.

Many text editors have programmable macros, but since Vim is keyboard-based, your programmed macros are usually far more predictable and easier to understand.

As it loads the whole file into RAM, replacing all string occurrences in 100 MB+ files is quick and easy. Every other editor has sort of died during that. It is extremely fast even for cold start. Vim is light-weight and very compact. In terminal, it only uses a small amount of memory and anytime you invoke Vim, it's extremely fast. It's immediate, so much so you can't even notice any time lag.

This makes Vim the definitive resource for every environment (Ruby/Rails, Python, C, etc.), or simply just provides more information in your view.

No need to memorize different key combinations for things like deleting the text inside of a block or deleting the text inside of a pair of quotes. It's just a series of actions, or nouns and verbs, or however you prefer to think about it. If you want to delete, you select "d"; if you want it to happen inside something, you select "i"; and if you want the surrounding double-quotes, just select ". But if you were changing the text, or copying it, or anything else, you'd still use the same "i" and ". This makes it very easy to remember a large number of different extremely useful commands, without the effort it takes to remember all of the Emacs "magic incantations", for example.

Vimtutor is an excellent interactive tutorial for people with no prior experience of Vim. It takes about 30 minutes to complete.

Vimscript provides a rich scripting functionality to build upon the core of Vim. When combined with things like Tim Pope's Pathogen plugin management system, it becomes easy to add support for syntax, debugging, build systems, git, and more.

If you happen to be logged into SSH, you can use Vim in a terminal. It can also run with a GUI too.

And will be supported for many years to come.

Vim's somewhat steep learning curve is more than made up for once you've mastered a few basic concepts and learned the tricks that allow you to program faster with fewer cut/paste mistakes.

The fact that very few, if any, people claim to be a "Vim Master" is a testament to the breadth and depth of Vim. There is always something new to learn - a new, perhaps more efficient, way to use it. This prevents Vim from ever feeling stale. It's always fresh.

Vim allows users to include many features found in IDEs and competing editors, but does not force them all on the user. This not only helps keep it lighter in weight than a lot of other options, but it also helps ensure that some unused features will not get in the way.

Interaction with Vim is centered around several "modes", where purpose and keybindings differ in each.
Insert mode is for entering text. This mode most resembles traditional text entry in most editors.
Normal mode (the default) is entered by hitting ESC and converts all keybindings to center around movement within the file, search, pane selection, etc.
Command mode is entered by hitting ":" in Normal mode and allows you to execute Vim commands and scripts similar in fashion to a shell.
Visual mode is for selecting lines, blocks, and characters of code.
Those are the major modes, and several more exist depending on what one defines as a "mode" in Vim.

All Linux distributions out there will have Vim built into them, which is highly convenient!

If you use Vim long enough, it will rewire your brain to be more efficient.

Vim does not only offer unlimited undo levels, later releases support an undo tree. It eventually gives the editor VCS-like features. You can undo the current file to any point in the past, even if a change was already undone again. Another neat feature is persistent undo, which enables to undo changes after the file was closed and reopened again.

Starting with Vim 8, a package manager has been built into Vim. The package manager helps keep track of installed plugins, their versions and also only loads the needed plugins on startup depending on the file type.

As with all vi-like editors, Vim provides a modal paradigm for text editing and processing that provides a rich syntax and semantic model for composing succinct, powerful commands. While this requires some initial investment in learning how it works in order to take full advantage of its capabilities, it rewards the user well in the long run. This modal interface paradigm also lends itself surprisingly well to many other types of applications that can be controlled by vi-like keybindings, such as browsers, image viewers, media players, network clients (for email and other communication media), and window managers. Even shells (including zsh, tcsh, mksh, and bash, among others) come with vi-like keybinding features that can greatly enhance user comfort and efficiency when the user is familiar with the vi modal editing paradigm.

Since Vim 8, Vim can exchange characters with background processes asynchronously. This avoids the problem of the text editor getting stuck when a plugin that had to communicate with a server was running. Now plugins can send and receive data from external scripts without forcing Vim to freeze.

It is called "registers".

Using vim not just increase your productivity, but helps you flex.

WebStorm integrates with Node.js to allow for running, debugging, and unit testing of Node.js apps.

To make sure your code can be easily maintained, you must first be sure to make it clean and tidy. This is the part where WebStorm really helps you. It automatically refactors your code by performing functions on it, such as extraction of variables, moving files, inline variable extraction, etc.

WebStorm comes bundled with JSHint and JSLint. JSCS, ESLint, and Closure Linter can be installed via npm. They register as inspections and are customizable through IDE settings. They run automatically and will highlight potential issues. Pressing alt+enter on an issue will allow the user to view suggested fixes.

WebStorm has two types of autocompletion: structural completion and word expansion.

Structural autocompletion makes predictions based on its understanding of JavaScript objects, while the latter tries to predict the word currently being typed based on previously typed words. Word expansion also works in comments and docstrings and it's similar to vim's omnicompletion.

Both types of autocompletion work extremely well, have little to no problems and are quite fast even when loading suggestions on the go.

The local history feature in Webstorm tracks all your local changes in the source code that you are making. You can use it to view changes that you've made to your code and roll back whenever necessary.

WebStorm offers typescript support for building typed JavaScript applications which improves refactoring and code completion, as well as helping to find bugs.

WebStorm includes support for Meteor, Angular, and React.

WebStorm includes a feature called Live Templates. Live Templates are predefined code snippets that can include variables. They're intended to increase productivity by reducing the amount of repetitive code that has to be written.

When you install WebStorm, it allows you to choose from other IDE's for it to base it's hot keys on. So if you are switching from another IDE, it makes it a very easy transition and productivity is not adversely affected by having to learn new hot keys.

WebStorm has a powerful visual git tool, allowing for easy commits, visual diffing, merging, push/pull, rebasing, and inspecting the VCS history of a project. GitHub is supported natively - you can check out a project directly from GitHub.

WebStorm has support for Grunt and Gulp task runners.

WebStorm (and really all of the IntelliJ IDEs) support the plugins throughout their plugin ecosystem which leaves you with 100s of tools to handle your automation tasks. There is a wide range of build-related plugins that help you by having pre-defined commands to execute with the click of a button. Out of any other IDE, WebStorm has by far the most coverage when it comes to tools for your development workflow.

The theme is very easy to customize to your liking. You can change font-size, colors, highlighting colors, and more.

Webstorm supports not just Git and Mercurial, but Subversion, CVS, and Perforce as well.

This integrates with other community tools like ESLint and editorconfig.

Code Templates are powered by Apache VTL (Velocity Template Language) and allow for includes, custom variables, conditional blocks, iterators, and live templates.

Webstorm comes with icons for many filetypes which makes it easier to find what you're looking for in the project list.

WebStorm has a built-in webserver that allows you to run projects from http://localhost:63342/ProjectName.

The IDE comes with a built-in terminal, a feature lacking in some lighter editors.

WebStorm has built-in support for CoffeeScript and Dart.

Karma allows you to execute unit tests and monitor code coverage. You can read more about using Karma with WebStorm here.

WebStorm has built-in support for Sass which is one of the most stable and powerful CSS extension languages.

WebStorm has a powerful debugger, with support for conditional breakpoints.

With the settings repository, you can easily enforce your development standards.

Non-commercial open source projects, and students and teachers (including classroom licenses) may qualify for a free license. There is a 50% off license for startups (under 3 years old). You can read more about it here.

It is able to specify for example node versions, which will be used to run task for current project.

Assists with configuration and understands module resolution.

Cordova allows for building native mobile applications via HTML, CSS, and JavaScript.

Autocompletion, syntax-highlighting, refactoring, and pub integration for Dart are supported in WebStorm.

Autocompletion, syntax-highlighting.

It may seem like a complex IDE and it does have a lot of functionality, yet it uses way less RAM than barebones-looking, Electron-based IDEs.

Makes adjusting an existing or creating new themes a breeze. Especially due to things like inheritance, as well as easily exporting/distributing/importing the color settings which really only store where on deviates from the defaults (thus the resulting files are very small and relatively human-readable).