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.
Ranked in these QuestionsQuestion Ranking
Pro Works in terminal over SSH
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.
Pro Extremely portable
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.
Pro Keyboard-based, mouse-free interface, and trackpad support
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.
Pro Lightweight and fast
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.
Pro Free and open-source software
Vim is open-source, GPL-compatible charityware.
Pro Macros increase productivity
Many text editors have programmable macros, but since Vim is keyboard-based, your programmed macros are usually far more predictable and easier to understand.
Pro Usable from a Terminal or with a GUI (GVim, MacVim)
If you happen to be logged into SSH, you can use Vim in a terminal. It can also run with a GUI too.
Pro Great productivity
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 most of Vim's functionality accessible without frequent awkward finger reaches.
Pro Once learned, it's very hard to forget
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.
Pro Everything is mnemonic
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.
Pro Tons of plugins/add-ons
This makes Vim the definitive resource for every environment (Ruby/Rails, Python, C, etc.), or simply just provides more information in your view.
Pro Has multiple distinct editing modes
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.
Vimtutor is an excellent interactive tutorial for people with no prior experience of Vim. It takes about 30 minutes to complete.
Pro Excellent performance
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.
Pro Can never outgrow it
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.
Pro Productivity enhancing modal paradigm
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.
Pro Built-in package management
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.
Pro Flexible feature-set
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.
Pro Asynchronous I/O support
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.
Pro Has been supported for a long time and will be supported for many years to come
Pro Donations and support to Vim.org helps children in Uganda through ICCF Holland
Pro By default in Linux
Pro On-demand, instant-access, real-time collaborative IDEs
Codenvy "Factory" feature enables developers to create temporary IDE workspaces with full code, build, test, deploy, and collaboration functionality that can be shared with a URL. Multiple people can work in the same workspace making code reviews and teaching simpler and faster. And there's no limit to collaborators.
Factories also work with external git repositories and can be shared with not registered users of Codenvy. It also allows counting how much a factory is used.
Pro Easy setup
Once an account is set up and the user has logged in, all that's needed to start is to pick a language, a framework and a PaaS. Codenvy also allows anonymous logins albeit with some important limitations.
Pro Powerful editor
Codenvy has a fast, secure browser-based editor that supports syntax highlighting, code completion, refactoring and more. It can be used to edit, build, run and debug projects. It even has multi-cursor support.
The layout will be familiar to most developer, especially those experienced with Eclipse, with a file explorer on the left, code on the right and tabs for builders, runners, terminal and events at the bottom.
Pro Fantastic Java support
All Java builders, syntax highlighting, class navigator, jump to package and declaration, and JavaDoc are present in Codenvy.
Pro Git support
Codenvy supports all Git commands through UI and Codenvy CLI.
Codenvy also integrates well with all major Git hosting providers including GitHub, BitBucket, GitLab. Sign up, sign in, repo cloning, uploading SSH keys are supported. Tutorials for integrating various providers can be found here.
Pro Can provide a custom runtime environment
Codenvy can provide a runtime environment to test and debug code. This can also be used to share work progress with a client.
Codenvy uses Docker as the runtime application and gives access to Dockerfiles allowing any environment that runs on Linux to be built. This allows using any database, reverse proxy or builder, etc. Codenvy even provides SSH access to running container in every image.
There's also a selection of pre-built environments to speed up the development.
Pro Partly open source
Codenvy is a full multi-user, multi-account, multi-tenant implementation of Eclipse Che.
Pro Has a fully functional free tier
Codenvy provides a fully functional free tier with 4 GB of RAM and unlimited workspaces, free and public projects and developers. Premium subscription start at $1/month and offers machines with up to 200GB of RAM. Codenvy also offers an on-premises solution that costs $300/user/year.
Pro Provides a terminal with root access
Codenvy offers a terminal with full root access into the machine. Since machines can be defined with Dockerfiles this gives the ability to create any custom environment for building, running or debuging and all the access that's needed to use it as a local machine.
Pro Complete build lifecycle
The IDE allows validating, compiling, testing, packaging and deploying.
It allows going to any box and pick up a project and work on it.
Pro Nice interface
Look and usability of Codenvy IDE are nice and pleasant.
Pro Integrates with a wide variety of tools
Codenvy offers first class support for code management, continuous integration, PaaS, and project management tools.
Pro Self-hostable (priced)
Codenvy has an on-premises solution that allows running it on own hardware and behind a firewall. The service costs $300/user/year.
Pro Lots of built-in templates
Pro Has Eclipse plugin
Codenvy can be plugged into Eclipse offering choice between online and offline builds. Plugin can be found here.
Pro Custom build system support
Codenvy allows setting up any build system via Dockerfile. Instructions on how to do it can be found here.
Pro Badge to start developing in one click
You can create a
.codenvy.json containing the Factory configuration which includes what binaries to install and how to set up the IDE, may be even start the development server. Then create a badge and put it on your GitHub repository and people can start coding and may be compile and run your server with one click.
Pro Quick support from staff
Pro Automation of contribution to GitHub projects
Codenvy provides contribution button that can be placed in Readme.md file on GitHub. It automates contribution to the Github's projects. User clicks this button and it opens a ready to run/edit version of the project in Codenvy. If a user makes changes, Codenvy takes care of everything needed for the contribution on GitHub.
- fork of the origin project on github
- add ssh keys to push to github
- create pull request in the origin project
- create factory url for review of this pull
- post this factory in pull request.
Then project's owner can use posted link to code review/run project with changes.
Pro One-click automation
Pro Can be used for Android development
Can be used for android development by adding Eclipse plugin.
Pro Easy projects sharing
Projects are share by sharing the link (public projects), adding access rights (private and public projects) and factory.
Factory allows to share projects along with build/run settings. To try run/review project recipient just need an URL. Factory also works with external git repositories so it allows share github/bitbucket/other git hosting projects. Recipient doesn't have to be registered. It also allows giving out a share button that activates the factory and counts how many times it is used.
Pro Developer workspace replicas
Codenvy can create a recipe for a developer workspace that includes the build and run environment configuration plus all the IDE plug-ins, syntax rules, policies and other items. Then version and store that with the code in a repository. Makes it impossible to get a code change that doesn't build and run.
Pro SSH Access
Can connect to the workspace via SSH for use with desktop editors.
Pro Provides Java debugger
Pro Includes Subversion support
Codenvy includes full subversion version control support.
Pro Portable workspaces
You can send someone a short JSON file and your whole workspace (projects, config and runtime) can be replicated for them in a separate container. Great for coordinating among team members.
Pro Install anywhere Docker runs
You can install Codenvy on any OS that has Docker running on it. The simple install syntax can work through proxies and even offline.
You can use this for proxy install:
You can use this for offline install:
Con Difficult learning curve
You'll spend a lot of time learning all the commands and modes supported in Vim. You'll then spend more time tuning settings to your needs. Although once it's tuned to your needs, you can take your
.vimrc to any machine you need and have the same experience across all your computers.
Con Poor support for external tooling
Many plugins depend on optional Python and Lua features, which may or may not be included in whatever binaries are available for your system. And without platform-specific hacks, it is difficult for plugins to operate in the background or use external tooling.
Con Poor feature discoverability
Though basic features like syntax checking, autocompletion, and file management are all available out of the box or with minimal configuration, this is not obvious to new users, who might get intimidated or assume they need to install complex plugins just so they can have this functionality. Other features new users might expect to find embedded in Vim, such as debugging, instead follow a UNIX-style model where they are called as external programs, the output of which might then be parsed by Vim so it can display results. Users not familiar with this paradigm will likely fault Vim for lacking those features as well.
Con Doesn't play nice with the system cut/paste mechanisms
This can be worked around if you disable mouse for insert mode. You can then right-click your terminal and use paste like you would anywhere else in a terminal.
Con Works poorly out of the box with right-to-left
Con Once you're used to it, you won't like other editors
When your fingers have learned Vim's keyboard commands, you'll find yourself reaching for them even when using other text editors. You'll get frustrated every time you have to reach for the mouse or move your cursor letter by letter with the arrow keys. You'll notice every time a Vim feature would save you time and tedium, and you'll wish the editor you're actually using had it. You'll wish the editor was Vim. You'll wish everything was Vim. You'll wish this imperfect world we live in could somehow become just a little bit more graceful, a little bit more elegant, by adopting modal text editing as a common paradigm. You'll wish desperately that this world was that better one. But it isn't. It isn't. And it never will be.:wq
Con Slow when opening files with very long lines
A lot of very long lines can make Vim take up to a minute to open files, where a few other editors take only seconds to load the same file.
Con Foreign keyboards have a hard time on Vim out of the box
A lot of frequently-used keybinds are way harder to access on foreign keyboards because they use different layouts.
For example, Germans use the QWERTZ layout, while French use the AZERTY.
Con User must remember commands instead of point at them in a menu
Con Unintuitive mode switching
Con No smooth scrolling
Even with the GUI version, the lines jiggle line-by-line. If you are used to smooth scrolling, this is very annoying, especially when working with larger files.
Con Consume brain energy for editing that should be used for logic
Text editing in vim is awesome, but it requires thinking about combination of commands. In other editors, you don't have to think about how to delete this part of code. You just think about how to implement a feature, what is a good design for this code. Even after you get used to using vim, it still requires your brain for editing.
Con High effort to customize
Con Lacks two-factor authentication
Con No SSH, FTP mode
For example, "Code everywhere" allows using SSH, FTP as base of project. In Codenvy it's possible only through VM.
Con No custom keyboard shortcuts
No possibility to create custom keyboard shortcuts.
Con Non-optimistic UI, typing results in letters being sent to server and back and then they show.
Con Slow installation by default
Trying to install with "npm install" and the server restarts before the installation. However, you can circumvent this by using
npm install --no-bin-links.
Con No IE support
Does not support Internet Explorer and no official plans have been publicly announced for its addition.