>Without measuring it A/B I cannot guarantee anything. You don't need to guarantee anything; I know my navigation and coding are way faster my way than if I we

>Without measuring it A/B I cannot guarantee anything. You don't need to guarantee anything; I know my navigation and coding are way faster my way than if I were to ignore my shortcuts. >And I don't think they were keyboard un-savvy As a sister comment to your mentions, MOST users, even developers, are still extremely limited in the number of keyboard shortcuts they use. I'm an outlier. If I want to save, my fingers hit Ctrl-S before I could even FIND where the mouse pointer is on the screen. Same with Ctrl-A for Select All. Or Shift-Ctrl-Left for select the previous word. No A-B testing required; it's seconds using the mouse for any of those, and 300-700ms for the keyboard. And those aren't even my most powerful shortcuts; they're just the ones ANYONE can use on Windows. If you get into "complete this word from [above/below] in this file", "jump to definition of this function" or "show references for this function", or "jump to previous bookmark", or "set bookmark" even, all of these are sub-500ms key sequences that would all take longer than a second if I had to use a mouse. It's not even close. Part of the problem with the study is that it was comparing using shortcuts vs. mouse on the Mac, where shortcuts are far less useful than they are on Windows. Navigating through menus by keyboard is easier for me with the keyboard on Windows as well; that's not even an option on Mac.