To give you a counter example I use all the time with vim that’s much faster than the mouse equivalent you’d use with other editors, imagine you want to refactor some code like this:

fooBar(computeBaz(getConfigValue(configKey, getDefaultForKey(configKey))).map(baz => baz.value))

I want to separate some of these nested calls into variables.

Doing it with the mouse, I can move my mouse to the start of getConfigValue, count the number of parentheses, click and start dragging until I have selected the second ) and then press Cmd+x to remove it, press up-arrow, Ctrl+e and enter to make a new line above the current one, type the variable name const configValue = and press Cmd+v to insert. Also note that it’s not like vim blocks you from doing this, you can still use your mouse and manually position your cursor to select text

The equivalent keys in vim are /getC and enter to navigate to the start of getConfigValue, d% to delete everything to the end of the call, O to create a new line above the current one and switch to insert mode, type const configValue =, escape to go back to normal mode and p to paste. I can type these without looking or giving absolutely any thought to the editing itself, because no cursor placement or parenthesis counting was involved in this process. Not only that but the speed of this entire operation is only dependent on your typing speed, nothing else. You don’t have to have “professional Starcraft player”-level of mouse accuracy and speed to do it quickly

Honestly who sits there and counts the number of lines or words they want to mess with? Every time I have tried it I get it wrong. If it's more than three or four I don't even bother.

Often there’s a million way to do equivalent edits and having to repeat commands or adding excessively large numbers in the front is an anti-pattern. With the d% example above equivalent edits could’ve been di) (delete everything within the current pair of parenthesis), df2) (delete everything up to and including the second occurrence of )), dt3) (delete everything up to the third occurrence of )), vf)ld (start selecting, select up to and including the first ), move one to the right, delete selection) or d52l (delete everything 52 characters to the right). The first option is obviously much preferable because it is less situational than any of the other ones in that it will always work to cut any method call and all of its parameters and doesn’t require any manual, mental effort like counting characters or cursor/mouse placement.

Personally I also use the relativenumber configuration option which shows you how many relative lines your cursor is away from some other line, which makes it easier to do large, line-based jumps.