The killer feature of Vim
If you open a Vim file, move the cursor to desired location and start typing, the text on the screen will be anything other than what the user wanted to do. A momentary twinge of panic mixed with anger will pass quickly enough, because the file is no saved, so you can just power off the computer, turn it back and googling.
Google, it appears that for the transformation of Vim in the normal editor you need to click i. Only save predatirovaniya the text, before you repeatedly press escape, and then call w. And to close it, you press escape and then type :q. The heavy legacy of the past. Well, Vim is everywhere.
But in some of the articles telling you how to spend 5 minutes in Vim and stay alive, is sure to be written that Vim is the best text editor in the world. And it turns out that people in this program. That is, of course, write code. That is, in the 21st century, in any time, you can download Visual Studio, Intellij Idea, or, God forgive me, Eclipse, and they write code in Vim. Voluntarily.
so the IDE facilitates the work of the programmer, to abandon the use of the IDE now only with very good reason. And if some refuse to IDE in favor of Vim, so there must be something steeper automatic refactoring, integrated debugger steeper, steeper substitution of imports, and integration with version control systems.
I Wonder what such features are in Vim, which is not even in the IDE, not to mention the banal notepad++?
Sad, but if you ask this question of the average Vim guru-of course — he simply will not understand. You can verify this reading the comments on Habre and generally climb on the Internet. In response to the question, what is good about Vim, I often write that you can delete the word by typing diw, and if you don't want to delete, and I want to highlight, then type viw. Well, that is, in the first case in the early d, the second v, but then here and there iw, which means inside word. How wild is that! I exaggerate, of course, but it seems to be true.
the
But programming it like?
Questioner usually says — Vim because somehow cope with the tasks that usually solves the IDE. I wonder how? He answered that in Vim there are lots of awesome plugins, but they need to install and configure.
What are these plugins better than the opportunities provided by the IDE, figure out usually fails, and occasionally manages to find out that the IDE slows down.
Then everything becomes clear, the person who wanted to know why vim recommends that the second side discussions to buy a faster computer and is eliminated from the conversation.
meanwhile, it would be worth to put the question directly.
For some features of Vim, users are willing to tolerate such fatal flaws as several modes of operation, the need to memorize a bunch of keys, and voluntarily refuse to use the shooter?
the
in fact, just the opposite
It's not about features of Vim users are willing to tolerate regimes, and in order to continue to use the modes, the user sawing the new features in Vim.
Yes, exactly. What at first glance seems inherited medvezhut ' — in fact, because of what Vim anyone wants.
You may think that there is nothing good in these modes is not and can not be. Suppose even that the way it is. Nevertheless, the use of Vim because of them, everything else is secondary. Actually this is the main and only idea of the article.
the
not a fatal flaw, a killer feature.
a simple editor to move the cursor to the end of the word needs to hold down Control, and then without releasing it, move the hand to the arrows and press the right. In the editor better, you can click not right and any key on the alphanumeric part of the keyboard, for example d, but Control will still have to hold. And in Vim you just need to click e. Users of Vim appreciate the opportunity to conduct manipulation with the cursor and text without having to keep it clamped when modifier keys or keep your hands away from home row. It relaxes you.
And if you want to understand what is good in Vim, you need to try to understand what's great about the modes, and figuring out which features are in plugins and, especially, not to try to understand what these features are better than those that provide the IDE.
And if you want to prove to someone that Vim sucks, they need to prove that the modes are crap. Those who use Vim, it's actually never clear.
the Opposite, by the way, is also true. If you want to explain to someone why do I need Vim and why is it so wonderful — talk about plug-ins useless. Plugins in the IDE, not worse. In addition, if to port plugins from Vim into some IDE, you cannot use it instead of Vim. For this it is necessary to carry the main modes.
the
Instead of an epilogue
Perhaps someone might say that writing an article for the sake of such trivia is overkill. I thought so too, but the picture described above, I watch for a few years.
Between the fans of Vim, and the rest of the world there is some sort of Grand and it is completely stupid misunderstanding, and I hope that when I meet him next time, I would rather give a link to this article.
