My introduction to keyboard shortcut navigation (like, heavy use of keyboard shortcuts) was through VSCode.
I've been gradually trending towards Vim as another tool, however, full adoption of Vim is not an "all-or-nothing" proposition for me.
VSC already has so much built into it; and all this conversation about not taking your hands away from the home row is BS... my counter argument to those arguments is: plenty of common commands in VIM require pulling your hands off the home row.
One place where VSC could really improve is making the customization of keyboard shortcuts simpler. I already know about recording my keystrokes to find the command and context, but customizing a key chord to a context is less than intuitive. What on earth are the various contexts I could use? A little help would be appreciated, Microsoft.
As far as VIM.... heavy usage leads to greater ability. Years of usage would definitely accelerate coding. For now though, I use it to pop open one-off files for quick checks, simple edits of config files, and the random simple edits.
> VSC already has so much built into it; and all this conversation about not taking your hands away from the home row is BS.
VSC is a very good tool. And if someone needs to be productive right away, it's easy to get him going. Vim has a steeper learning curve, but it is easy to make it your own, perfectly suited to you and your projects. As you said, it's not one or another. I use VSC now and then, but going back to my Vim setup is always a delight.
The arguments about the home row are valid. With VIM, text on the screen become an extension of your thinking. And your finger and the keyboard are just the medium that connects both. How I do an action is how I think about doing it. Moving around and editing text has the same cognitive load as entering new text. The things that require me to go away from the home row are unusual operations that also require my full focus and attention.
Interesting. It's comments and conversations like this that keep VIM on my horizon and keep me working to incorporate more of it in my daily practice.
I will say this: customization of shortcuts in VIM does seem easier than in VSC (strictly regarding the context settings I was complaining about in VSC).
Perhaps in time the utility I find in VIM will grow, given enough effort. Cheers.
My introduction to keyboard shortcut navigation (like, heavy use of keyboard shortcuts) was through VSCode.
I've been gradually trending towards Vim as another tool, however, full adoption of Vim is not an "all-or-nothing" proposition for me.
VSC already has so much built into it; and all this conversation about not taking your hands away from the home row is BS... my counter argument to those arguments is: plenty of common commands in VIM require pulling your hands off the home row.
One place where VSC could really improve is making the customization of keyboard shortcuts simpler. I already know about recording my keystrokes to find the command and context, but customizing a key chord to a context is less than intuitive. What on earth are the various contexts I could use? A little help would be appreciated, Microsoft.
As far as VIM.... heavy usage leads to greater ability. Years of usage would definitely accelerate coding. For now though, I use it to pop open one-off files for quick checks, simple edits of config files, and the random simple edits.