Did I say Vim isn't for everyone? I certainly felt that way the first couple of time I tried it. After several failed attempts over the years, I fi...
For further actions, you may consider blocking this person and/or reporting abuse
I have my own list of plugins in Vim, but I was so used to graphical interfaces that, every time when I try to cut and move a long snippet to different place, I feel I cannot do that in Vim well. That's very annoying. :(
But Vim is really fast! Still thinking how to use Vim instead of VSCode.
I think the transition for me is graphical -> shortcut keys -> vim commands. I already knew how to do quite a bit with shortcut keys (like ctrl + c for cut and ctrl + v for paste) before I started vim. Some of my first wins with vim are by replacing the shortcut keys I normally use with vim commands (like x for cut and p for paste). This got me feeling productive pretty quickly.
Great tips, I agree with them all and love Vim as well. For anyone looking to learn I highly recommend the now free Upcase course Onramp to Vim.
It is available here: thoughtbot.com/upcase/onramp-to-vim
They also have a great video on Neovim and Vim 8 as well as one on using the terminal effectively.
What really helped me when I started with vim was to disable arrow keys in .vimrc, took me a couple of days to get used to it, but everything was much easier after that :D
Vim rocks. 10x better and faster than electron-based bloatware like VSCode or Atom.
I agree it is much faster, although I felt the speedup does not completely outweighs the other things VSCode has, like a debugger, and the huge ecosystem of quality extensions. If you work with technology like TypeScript VSCode makes it really nice with all the functionality provided by the language server. Overall I could jump into a file with vim and edit away, I do this with documentation (in markdown) and git workflows a lot. For navigating a large codebase and figuring out what I need to do I would open VSCode/WebStorm.
I've always wanted to use it, but in the end couldn't go trough with it. Currently I use it as git commit message editor and in the terminal, but my daily driver is still VS Code.
I use the VSCodeVim extension in VSCode (marketplace.visualstudio.com/items...) as my daily driver. It isn't perfect Vim but pretty close for most of what I want to do. Once the extension is installed you can toggle vim mode on/off via the VSCode command menu (ctrl + shift + p then type
toggle vim mode). It should hopefully be less daunting than vim in the terminal.