3 ms·
An old-schooler would be the one asking, "why do I need a mouse?" Anyway, it sounds like you're asking, "Why are keyboard shortcuts faster than moving a mouse
by blunte 10y ago
An old-schooler would be the one asking, "why do I need a mouse?"
Anyway, it sounds like you're asking, "Why are keyboard shortcuts faster than moving a mouse to a location and then clicking [and potentially having to move to another location, such as the menu that just dropped down, and clicking again]?"
Does this really need an answer?
- ryandrake 10y agoYou forgot even more inefficiency: Lifting your hand off the keyboard and moving it to the mouse, [insert your above steps], then moving back to the home row.
- blunte 10y agoI didn't forget. I just didn't feel like enumerating what I think are obvious and commonly accepted facts :). It really comes down to thought->muscle memory of keyboard shortcuts, especially those which don't require moving hands away from the home keys, vs the activity of reaching over, taking the mouse, driving it to a certain location on the screen, and then clicking. It should be obvious which will be faster.
- pix64 10y agoIs scrolling through source code really faster line by line?
- ryandrake 10y ago80j Just scrolled down 80 lines
- noctuid 10y agoThat's what you do with a mouse though. With a keyboard, you can move by semantic units (like a paragraph or function), use fuzzy search to jump to a specific function, etc.
- blunte 10y agoThere are so many keyboard options for moving through source which you don't have with a mouse... - Page up/down (and especially with home row shortcuts like in Emacs and Vi) - Brace match jumps - n line jumps up or down in Vim - top/mid/bottom of view jumps - page shifts up and down without moving the cursor - top/bottom of file jumps - jump directly to a line in a file ... and more Seriously, put an Emacs or Vi power user next to a guy with an IDE and a mouse, and it's no contest.
- chousuke 10y agoAs a vim user, I don't really find myself needing to scroll "fast" ever. Instead, there are three common cases: 1) I'm reading through code, and scrolling one line at a time with j/k is fast enough. 2) I'm looking for a specific point in the code, in which case I use search to get to it. 3) I want to go to the bottom or the top of the file, in which case G/gg are much faster than scrolling. Sometimes I might use Page up/page down to skim a file, but that's relatively rare.
- btschaegg 10y agoActually, this is also a point worth stressing for people without Vim-experience: Searching is a "first-class citizen" (as the FP-guys put it with functions). It's only ever one to two keystrokes away. You press '/', enter your phrase, and press ENTER. Stepping is done with 'n' and 'N'. There really are no convoluted hotkeys for this - which means that you do it much more liberally once you're accustomed to it. Also there's '*' and '#' to quickly find the next/previous positions of the word your cursor is currentl located on. The same thing applies there.
- lorenzhs 10y agoNo problem at all if you use a TrackPoint. I don't even have a mouse, I use the ThinkPad USB keyboard at work which includes a TrackPoint. I know some people dislike them with a passion, and they don't look fashionable, but I can't use a keyboard without one any more.
- deleted 10y ago[deleted]