Earlier quoted context omitted.
Hm, I doubt the precision can match and avoid under/overshootings, especially at high enough repeat speed to match, and it's a global change that can affect even regular typing, so you're suggesting specialized training (to minimizeerrors) for a less effective workflow
The main issue with precise jumps (for me) is that they require you to - already exactly know where you want to go - figure out the relative distance either by looking to the side at relative line numbers or calculating - move your hands to the numbers row to input numbers and back (I don't have small hands, but that still translates into a small amount of arm movement for me). Whereas just using repeat input on jklh…
Same as with moving down by 1x10? How are you even choosing cursor direction if you don't know where to go to?
> - figure out the relative distance either by looking to the side
Ok, how is that an issue? You also have to figure out the distance by looking down when moving down with the arrows, so eyes still move?
> move your hands to the numbers row to input numbers and back
No, you could maintain your hands on the home row and use a numpad layer containing it
> imagine you had to tell your hand "move 10 centimeters left"
Imagine you had to tell your hand "move 1 centimeter left 10 times"? The mouse is that extension where you don't "move by 1 pixel X times" and move in an analog way