3 ms·
Raskin's version of Tog's point (in the article) is more nuanced - switching between keyboard and mouse is the expensive thing and even more "perceptually under
by eichin 3y ago
Raskin's version of Tog's point (in the article) is more nuanced - switching between keyboard and mouse is the expensive thing and even more "perceptually underreported" than either of them on their own.
(That said, my workflow involves cloning as often as a couple of times a day if things are going well; SSD space is basically free, and --reference-if-able means a clone-per-branch is cheap, and my "work on this" script spins up a docker image and a fresh build too, after cloning and switching. So, while the described shortcuts would make sense in my "world", I've already automated way beyond that :-)
- pmontra 3y agoTo test my intuition: as a two-to-five clones per day person, do you think that you could benefit from that gesture, if you didn't need to automate the process around it?
- eichin 3y agoIf I were already using the mouse for the cut&paste step, yeah, it would flow from one to the other. (In practice, I do both the cut-whole-url and paste steps entirely from the keyboard anyway, so using a gesture at all would be flow-breaking. But if I were mousing for the surrounding work it would make sense.) (I've actually had mouse-based workflows sometimes - I normally prefer a trackpoint, not as a mouse substitute but as "save me from doing weird contortions to keyboard-orient absolutely everything" - but the times when I've been a tech lead and spending excessive time in spreadsheets and planning apps, I've hooked up a relatively fancy mouse and started to develop more mouse-oriented shortcuts. Fortunately I've escaped from that :-)