A little bit about VIM and IDE
One, I have no doubt, a good man and vim-er with experience published an article today that the regimes are a killer feature of vim. Let me disagree and work as captain Obvious.
It is not overloaded with unnecessary functionality. Seriously, IDE-people, how many percent of the functionality of your IDE do you use? 25-30%? The VIM feature is here in a total configuration, and not only in a general sense, but also separately for each language / project. You can download some plugins for c, others for js, others for go. You can use four spaces in one project, and eight in the other. Using different VIM configurations for each language \ project. As was rightly noted in the comments to the previous article, this was not laid out in vim, but it happened.
Yes, language support and more convenient features for refactoring code and smoothing smoothies are more closely integrated into your IDE. This is good, convenient and works, until someone has bothered to write an IDE for your language, or at least a plugin to support the language in which you write. But imagine, for example, you mainly write in C ++, and it became necessary to look at the JAVA code. Will you install a separate IDE or plugin? In the case of vim, you simply open the code and “out of the box” will get minimal language support (lights, folding of blocks, etc.)
IDE is a good choice when you dig in 2-3 languages ​​and don't leave anywhere.
In the comments to that article, it was repeatedly suggested to use the vim plugin. A good idea if you decide to move from IDE to vim, but in the opposite direction it does not work well - you know the hot keys and Vim combinations, the vim configuration is “licked” by years of work, and it turns out that your config works a maximum of half that you have to combinations, which, as a rule, are not convenient, make “raspaltsovki” on the keyboard and from time to time all the same pull the hand to the mouse.
')
Your config is “licked” and smooth, you perform all the necessary operations without even thinking about them, your fingers do everything themselves - this is how vim-er works with the experience. Seriously, when I need to, for example, move the block of code by 2-3 indents to the right - my hands do it themselves, when they ask me how to do this in vim - I “hang” for a few seconds trying to remember. With IDE, personally, I did not succeed - I had to be distracted by the mouse, remember which menu was the right item, get to it.
In vim, all operations are performed from the keyboard, and it is damn convenient. The combination of vim + tmux + i3 and the mouse 99% of the time lying around, but this is a topic for a separate article. What is the convenience of not giving up the mouse? Starting from the banal lack of movement of the hand between the mouse and the keyboard, ending with the fact that it is really faster. Type 2dw to delete two words faster than select them with the mouse and click Backspace \ Delete.
Modes are not a killer feature of vim, they are convenient, good, but, by and large, this is just one of two ways how to make the editor have rich functionality and be fully controlled from the keyboard. The second path is the emacs path.
To know vim is necessary, if only because vim or its ancestor vi is on almost any * nix machine.
Sometimes vim is the only way to fix configs on a remote machine.
Vim is a good and convenient tool, but it requires pre-configuration.
IDE - allows you to work with it, in most cases out of the box.
Vim - Powerful and versatile tool.
IDE - Powerful, but highly specialized tool
Vim - supports more languages ​​than you can remember
IDE - supports 1-3 languages, but does it better than VIM
If you still want to holivarit on Vim VS IDE, then do not forget - these are tools. You can sculpt the good and eternal, even with the help of awk, the question of what to use is just a matter of convenience and habits.
Vim is not an IDE
It is not overloaded with unnecessary functionality. Seriously, IDE-people, how many percent of the functionality of your IDE do you use? 25-30%? The VIM feature is here in a total configuration, and not only in a general sense, but also separately for each language / project. You can download some plugins for c, others for js, others for go. You can use four spaces in one project, and eight in the other. Using different VIM configurations for each language \ project. As was rightly noted in the comments to the previous article, this was not laid out in vim, but it happened.
IDE is also not vim, even with a plugin
Yes, language support and more convenient features for refactoring code and smoothing smoothies are more closely integrated into your IDE. This is good, convenient and works, until someone has bothered to write an IDE for your language, or at least a plugin to support the language in which you write. But imagine, for example, you mainly write in C ++, and it became necessary to look at the JAVA code. Will you install a separate IDE or plugin? In the case of vim, you simply open the code and “out of the box” will get minimal language support (lights, folding of blocks, etc.)
IDE is a good choice when you dig in 2-3 languages ​​and don't leave anywhere.
In the comments to that article, it was repeatedly suggested to use the vim plugin. A good idea if you decide to move from IDE to vim, but in the opposite direction it does not work well - you know the hot keys and Vim combinations, the vim configuration is “licked” by years of work, and it turns out that your config works a maximum of half that you have to combinations, which, as a rule, are not convenient, make “raspaltsovki” on the keyboard and from time to time all the same pull the hand to the mouse.
')
A little bit about the mouse, keyboard and VIM
Your config is “licked” and smooth, you perform all the necessary operations without even thinking about them, your fingers do everything themselves - this is how vim-er works with the experience. Seriously, when I need to, for example, move the block of code by 2-3 indents to the right - my hands do it themselves, when they ask me how to do this in vim - I “hang” for a few seconds trying to remember. With IDE, personally, I did not succeed - I had to be distracted by the mouse, remember which menu was the right item, get to it.
In vim, all operations are performed from the keyboard, and it is damn convenient. The combination of vim + tmux + i3 and the mouse 99% of the time lying around, but this is a topic for a separate article. What is the convenience of not giving up the mouse? Starting from the banal lack of movement of the hand between the mouse and the keyboard, ending with the fact that it is really faster. Type 2dw to delete two words faster than select them with the mouse and click Backspace \ Delete.
Modes
Modes are not a killer feature of vim, they are convenient, good, but, by and large, this is just one of two ways how to make the editor have rich functionality and be fully controlled from the keyboard. The second path is the emacs path.
Prevalence
To know vim is necessary, if only because vim or its ancestor vi is on almost any * nix machine.
Sometimes vim is the only way to fix configs on a remote machine.
Instead of conclusion
Vim is a good and convenient tool, but it requires pre-configuration.
IDE - allows you to work with it, in most cases out of the box.
Vim - Powerful and versatile tool.
IDE - Powerful, but highly specialized tool
Vim - supports more languages ​​than you can remember
IDE - supports 1-3 languages, but does it better than VIM
If you still want to holivarit on Vim VS IDE, then do not forget - these are tools. You can sculpt the good and eternal, even with the help of awk, the question of what to use is just a matter of convenience and habits.
Source: https://habr.com/ru/post/339988/
All Articles