5 ms·
Related: https://danluu.com/keyboard-v-mouse/ https://danluu.com/keyboard-v-mouse/ - "The widely cited studies on mouse vs. keyboard efficiency are completely b
by klibertp 3y ago
Related: https://danluu.com/keyboard-v-mouse/ https://danluu.com/keyboard-v-mouse/ - "The widely cited studies on mouse vs. keyboard efficiency are completely bogus."
EDIT:
More on topic: I tried, but the percentage of times when my stroke wasn't recognized was way too high for me. There's a customization variable that could help, but I have enough programmable buttons on my physical mouse[1] to get by with just them:
- scroll up/down
- tilt wheel left/right
- two small buttons for back/forward to the left of the left button
- dpi change button under thumb (can be made to send other events with Solaar)
So I can directly bind 5-7 commands that will work every time without risking the "stroke was not recognized" problem. And that's without modifiers and clever hacks like mouse3.el, which allow for (almost) directly exposing even more functionality. Strokes/gestures are slower and less reliable than this. They probably can be helpful in some configurations (I wonder if Emacs on Android would be the perfect use case?), but I don't feel the need for them in my setup.
[1] https://www.logitech.com/en-us/products/mice/mx-ergo-wireless-trackball-mouse.html https://www.logitech.com/en-us/products/mice/mx-ergo-wireles...
- bloopernova 3y agoFor an even more configurable mouse, check out the Ploopy mouse and trackballs: https://ploopy.co/ https://ploopy.co/ Fully open source, the mouse (that I own) uses QMK for its firmware. Which means I can use key binding layers rather than single buttons. In other words, one button acts like a shift button that modifies the action of the other buttons. So I have easy access to page up/down, mission control (what was exposé in macOS), paste plain (shift+option+cmd+v), etc etc. I don't have anything Emacs specific on the mouse, but my keyboard (Keychron Q10) has several macro keys that I have meta-x and ctrl-g bound to.
- m463 3y agostrange. It is 3d-printed and fully customizable, but they only have right-handed. even the pcb seems to be right-handed.
- deafpolygon 3y agoAt 200+ euros, it puts a high barrier for entry. I might try it someday when I have more money, but I have other pressing things to buy first. :(
- klibertp 3y agoOh, that looks lovely! I'll need to check them out. > Fully open source, the mouse (that I own) uses QMK for its firmware. Which means I can use key binding layers rather than single buttons. On this topic, I bought a System76 laptop this year, and I'm in love with its keyboard-configurator. The firmware for the keyboard is also fully open source, and the GUI configurator is really excellent. It's a little limited in WHAT you can bind (without going down the rabbit hole too deep), but there are no limits at all on WHERE you can bind it, and it's beautiful. I made both left ctrl and fn work as ctrl (I could have made fn into hyper, too) and this is the first keyboard where I was able to do that (my previous laptop, Thinkpad, could only swap ctrl/fn functions). Open source firmware FTW! :)
- Conscat 3y agoI am an avid Ploopy shill, but I can't convince anyone vaguely interested in libre peripherals to try it on account of the name "Ploopy". :/
- bloopernova 3y agoYeah, the name does pose a barrier to adoption, but I think the owner likes it like that.
- kqr 3y agoThe idea that command keys would consistently be slower sounds insane to me. When e.g. writing I regularly save my documents by keying in ctrl-s and that is demonstrably much faster than if I'd have to aim the mouse at the tiny File menu and the click and go down to "save".
- klibertp 3y agoYeah, I like the conclusion from the article I linked: > Unlike claims by either keyboard or mouse advocates, when I do experiments myself, the results are mixed. Some tasks are substantially faster if I use the keyboard and some are substantially faster if I use the mouse. Moreover, most of the results are easily predictable (when the results are similar, the prediction is that it would be hard to predict). If we look at the most widely cited, authoritative, results on the web, we find that they make very strong claims that the mouse is much faster than the keyboard but back up the claim with nothing but a single, bogus, experiment. In other words: it depends, and common sense is still the best guide. :)