[ajfjrbfbf]

I started with vimtutor, then installed IdeaVim in all my Jetbrains IDEs, it took me about a week to reach the same level of efficiency I had before.

I don't understand how some people can say the learning curve is too steep. Sure it's a bit annoying at first, but it quickly becomes natural, and you don't have to use all features at first. It has allowed me to improve my touch typing a lot. Learning a programming language is a lot more work but hardly anyone ever complain about it.

It's been maybe two months and I wouldn't think of using anything else than vim for serious code editing.

[sverhagen]

> I don't understand how some people can say the learning curve is too steep

I am doing fine with vim for basic editing tasks and use it a lot (mostly when I'm already in the command line). But there's just only so many shortcuts I'm capable of memorizing. This is not a problem for me exclusive to vim, of course. In IntelliJ I also sometimes find an amazing new function that I then don't keep using since I've already exhausted my limited "inclination" of learning new shortcuts. Also, I don't think my productivity gains at this point are going to come from faster input anyway. Sorry, vim, it's not you, it's me.

[40four]

I’m a full time vim user now, and I would say the ‘productivity’ gains are a bit of a pipe dream. That’s not the reason I would recommend anyone learn vim. The best reason for me is that vim is just fun.

When you finally become competent, it is an absolute joy to work with. It makes me think about editing in a totally different way. However the road to get to that point is not fun.

I started out with basic tasks in the terminal, & vimtutor reps. Then graduated to using a VS code plugin. I would turn it on for 10-15 minutes at a time a few times a day. Usually turning it off once I realize I wasn’t getting anything done :) But solid reps everyday over a few months and I got to where I learned more complex commands/ movements. Eventually I never needed to turn it off!

Then I began the configuration & plugin rabit-hole :)

[AlchemistCamp]

How many years have you been using it full-time?

Do you ever miss the global commands not implemented in VS code's plug-in? I still do sometimes, like this: https://youtu.be/46Evprns18M

[40four]

Full time a little over a year now I think.

Yeah that's a good point. After a while you do start to realize the limitations of the VS Code plugin. That video is a good example. But once I got to where I could edit at equivalent speed I was used to, I dropped VS Code completely. I looked at the plugin as 'training wheels'.

I'm not as hardcore as some. I still prefer to use GVim/ Macvim. I'm not an 'everything must stay in the terminal' purist. I know some who are, but I still like being able to use the mouse to bail me out sometimes, and always have access to the system clipboard without having to recompile vim :)

I don't go crazy with config & plugins, but I got my setup to where I have all the features I missed from VS Code, and that's enough for me.

There is always more to learn though. I feel like I've been complacent lately, so you have to remind yourself sometimes to make an effort to seek out more advanced techniques.

That video is a great example of some of the incredibly powerful things Vim can do! I'm a big fan of macros for repetitive tasks.

[Agentlien]

That's one of the strengths of Vim, though. There's a lot of structure to it, so you don't need to learn nearly as many shortcuts as you otherwise would.