In Praise of Chorded Input
v21.io
v21.io
I've also noticed the preference come up when playing games. Ideally, I would simply assign additional abilities to modified keys, but for the life of me, it's just simpler to assign them, one to one, to keys on the keyboard. My hand needs to move around the keyboard a bit more, but it has to contort a lot less.
Also, it's somewhat telling that some the fastest typists in the world don't use shift - they use caps lock.
ref. http://www.seanwrona.com/typing.php the final paragraph
Your hand is not anchored to the shift button. You can use one finger for the first press of capslock, and another for the second, based on where the previous and next letters are (this is a reference to the typist using any finger to hit any letter).
Using shift is still three actions: for the shift button it's a press and hold followed by a timed release, plus a press of the target letter. Given this, the "press press press" rhythm matches the rest of the typing flow better than "hold press release".
Since we're looking at competitive typists (what a world, eh?), they're probably not allowed such things when being measured.
Shift: Press -> hold -> release
Lock: Press -> release -> press -> release
Both cases require timing. I'm not convinced he's faster because of capslock, he seems to be faster in spite of it.
I also use a hybrid typing style. For example, the word "server". The first time I strike the "e" with my middle finger and the second "e" is with my ring finger, freeing my middle finger to type the final "r" because my index finger is still at the lower row after typing "v". Surely he uses this style of non-traditional touch typing for words like "Azure, Qatar, Zaire," but I think the flexibility of finger choice is the secret to success, not the capslock key.
I also imagine it makes typing out acroynyms a lot simpler as well. For example, I hold down left shift when I type NASA (left shift since I hit the 'n' with my right hand), and contort my left hand while being sure not to release shift to finish the word.
In any case, it's mostly my own conjecture - day-to-day I can't type very accurately without relying on coming back to home; without using the same fingers for the same letters all the time.
I get tripped off a bit when switching keyboards, between desktop and laptop. Still, it is worth the effort IMO.
Daily. Am I ever thankful that VIM is (mostly) the same across OSes. :/
Work: OSx
Play: Windows
Hobby: OSx terminal (effectively Linux)
The bigger problem for me is that muscle memory between OSes is broken by something as simple as "how to do I get to the head (or tail) of the current line I'm on?" On Windows, it's Home/End. OSx is Cmd+Left/Right. Terminal, it's Ctrl+A/E (or Home/End, sometimes).
It’s also Ctrl+A/E most places in macOS - they’re Emacs keybindings, and lots of those work systemwide in macOS.
On Windows, it takes you to the first character of the line you're currently working on.
Multitouch gestures are a form of chorded input, no? And one we’ve greatly under-explored, IMHO.
Probably mostly because people tend to be using either touchscreens that are mobile, or touch pads that are rather small, and so you can only fit one hand’s worth of fingers on the digitizer, and one hand’s fingers can’t (without training) do too many different things at the same time. So mostly we come up with gestures that move some or all the fingers of the hand in concert.
But if you had a digitizer surface that had room for two hands, you could do a lot with that. Moving a finger of one hand in a circle while the other swipes toward/away from it; “unfolding” something by interlacing eight fingers in a line and sliding them to opposite ends of the digitizer; etc.
(I think Apple could easily introduce these for people who own both an iPad and a Mac. It seems their Sidecar support is already moving toward this, as it sends native touchpad input to apps—acting, in est, as a large Bluetooth multitouch digitizer—rather than just doing HLE emulation + transmission of the particular gestures possible in macOS currently.)
And sure, that all sounds a bit mystery-meat at first—no clear affordances. But it’s not any more mystery-meat than voice navigation is. Voice navigation is a “grammar” on top of regular spoken-language words; you expect the user to learn language at some point. Similarly, a “vocabulary” of multitouch gestures could all be taught to the user at some point—even practiced in an OS-shipped program resembling a typing tutor. (Back when mice first became prominent, OSes shipped with mouse-requiring games specifically to serve as mousing tutors!) Then you just have to teach the users visual/symbolic mnemonics for these gestures; and then you can use those symbols as accelerator indicators in your regular menus and label text.
(Oh, and don’t get me started on what’s possible with a depth-of-field sensing camera, ala Windows Hello. I’m constantly surprised that competition isn’t already heating up to be the first OS to natively support American Sign Language watched-gesture input.)
Eh, the reason why I'm into modal editing is precisely that it doesn't require much chording. That's also why I've configured my keyboard to write all the ascii printable symbols without chording, and shift is sticky so I don't need to chord it to write a capital I.
I could imagine having a handful of simple chords, but not much more. The problem I see with chording is that it imposes timing restrictions that allow room for misinterpretation when you're typing things too quickly. And generally I find it more difficult & tense to press more than one key simultaneously.
If anybody has a solution for custom chords on a qwerty that doesn't cost hundreds of dollars I'd love to hear it!
That said, the type of soldering required is quite easy and if you have a friend with a decent iron and some time they can teach you the required skill quite quickly.
I'm guessing at some point they got approved as an assistance device, because now they sell for $500. Presumably it's insurance companies that are paying at this rate.
Its possible people will just get used to typing on simulated virtual keyboards, like they did for on-screen keyboards on mobile. However, simulated QWERTY input in VR is significantly worse than it is on mobile, since unlike on mobile there's no tactile feedback at all; not even the rudimentary feedback of your fingers touching a flat surface. Whether that added inconvenience is enough to overcome the friction of users needing to learn a whole new input method to type with though is uncertain. In the short term I don't think it is, but long term? Hard to say.
Still, I think there's a lot of room for improvement of human interfaces (at least until we hopefully someday get neural interfaces which bypass hands and even eyes).
Mobile devices lack good input methods. There’s a possibility they might prove useful for those on the go.
“ Over 17 Billion (17.1529*10^12) possible chord combinations per profile."
36! is a pretty large number as well. ;)
This isn't an attempt to denigrate the product, it does look nice. One of my favorite chorded input methods was the old steam controller text input that combined 8 positions on the left stick with the right 4 face buttons of a standard controller. But it's design is closer to a standard keyboard than chorded keyboard.
That’s why I mentioned usage with mobile devices.
I’d like to sit on a park bench on a nice spring day and write my blog with my phone.
Starbucks, library, picnic table, deli, ....
Personal preference and all that. :)
I use it daily and it is pretty convenient. There are other chords too, but those are the big ones.
And one of the things that makes me miss proper three button mice.
I don't understand why mouse buttons need to be so large. Indeed, keys are much smaller, and the thumb buttons in mice are still much smaller. That's not a problem. Every mouse I've had has a comfortable spot between the two main buttons and the wheel where you could fit the third button..
asking important question, can wha-wha be incorporated? Markdown, are you there?