> Seriously you type so fast and code at the speed of thought that a little glitch here is like making a mistake with a Formula 1 car in the Monaco Grand Prix?
Please, don't take it to the other extreme.
The way I use vim, I still use arrow keys instead of hjkl. I usually don't do 8k or 3j. Yet daW, cs"', cit, /foo<CR>whateveroperationnn.nnn.n., /bar<CR>qawhateverbutmorecomplexqn@ann@a are part of my daily routine†.
Clicking around or moving with arrow keys to operate on well defined text objects feels like hunt-and-peck typing, while the argument is that the only true way to vim is knowing it, similar to touch typing. Yet between hunt-and-peck and touch typing, there's a continuous world.
I type at a reasonable speed, and I use vim at a reasonable speed. I'm not aiming for purity, I'm aiming for usefulness.
In general, Sublime Text does a vast and extensible yet at any given point in time fixed number of things well, while vim allows for composability, and hence even with a default setup and few things known, a great deal can be done already. This is what empowers me, not the home row touch typing stuff, not the navigation speed, but the quality of the dialog I can have with the editor.
† I know about multi-cursors in Sublime Text, and Ctrl+D, but Ctrl+D doesn't allow you to skip, and the whatever_operation you want may or may not operate on the search itself (which could actually be an ack search), and can operate on objects ST doesn't even know about. This allows me to do free-form refactoring without relying on fixed-form refactoring routines and plugins (i.e not just a glorified search and replace).
Please, don't take it to the other extreme.
The way I use vim, I still use arrow keys instead of hjkl. I usually don't do 8k or 3j. Yet daW, cs"', cit, /foo<CR>whateveroperationnn.nnn.n., /bar<CR>qawhateverbutmorecomplexqn@ann@a are part of my daily routine†.
Clicking around or moving with arrow keys to operate on well defined text objects feels like hunt-and-peck typing, while the argument is that the only true way to vim is knowing it, similar to touch typing. Yet between hunt-and-peck and touch typing, there's a continuous world.
I type at a reasonable speed, and I use vim at a reasonable speed. I'm not aiming for purity, I'm aiming for usefulness.
In general, Sublime Text does a vast and extensible yet at any given point in time fixed number of things well, while vim allows for composability, and hence even with a default setup and few things known, a great deal can be done already. This is what empowers me, not the home row touch typing stuff, not the navigation speed, but the quality of the dialog I can have with the editor.
† I know about multi-cursors in Sublime Text, and Ctrl+D, but Ctrl+D doesn't allow you to skip, and the whatever_operation you want may or may not operate on the search itself (which could actually be an ack search), and can operate on objects ST doesn't even know about. This allows me to do free-form refactoring without relying on fixed-form refactoring routines and plugins (i.e not just a glorified search and replace).