Wednesday, July 11, 2012

A keyboard just for me

We've had the QWERTY keyboard for ages. I learned to type on a real, honest-to-goodness manual typewriter with the QWERTY layout. I learned to program in BASIC on a Teletype ASR-33 (with a QWERTY keyboard), and 8080 assembly on a Heathkit H-89 (with a QWERTY) keyboard. All of these devices had the keyboards built in, part of the device itself.

The IBM PC came with a QWERTY keyboard (at least in the US). Unlike the previous devices, it had a detachable keyboard, and one could replace it with a different layout. (Not that many people did.)

I am sure that some folks still use the Dvorak layout. Some have called for a new standard.

With the invention of the smartphone and the tablet, we now have virtual keyboards. They appear on the display and are composed of programmable bits.

It strikes me that we don't really need a standard keyboard layout. When keyboards were physical things, hard-wired to the main device, a standard layout made sense. (Even when keyboards were mechanical components of manual typewriters, a standard layout made sense.) Physical keyboards could not be changed, and a standard let people easily move from one device to another.

With virtual keyboards we can create individual keyboards and let them follow us from device to device. When keyboards are programmed bits on a screen, it is easy to program those bits for our preferences. We don't need a standard keyboard that everyone agrees to use; better to have our custom keyboard to appear when we use the device.

Those custom keyboards can be any layout. They can be QWERTY. They can be Dvorak. They can be Dextr. They can be any of the above with slight changes. They can be wildly different. They can be programmed with additional keys for characters and glyphs outside of our normal set. (While I use the US layout, I often write the name "Mylène Farmer" and I need the accented 'è'.)

Beyond characters, we can add commonly used words. Android devices often add a key for ".com". We could add custom keys for e-mail addresses. When writing code, we could have special keyboards with keywords of the language ('if', 'while', etc.). Keyboards might interact with development environments. (We see something of this with the smart matching that suggests words as we type.)

I see little need to stay with the QWERTY layout. (Designed, long ago, to prevent people from typing too quickly and jamming the mechanical keys in a manual typewriter.)

Let my keyboard layout be mine!

2 comments:

Anonymous said...
This comment has been removed by the author.
Anonymous said...

Thanks for this helpful article, indeed there's no reason why we should stay with QWERTY layout. Specially if you're a beginner, is there a need for you to suffer the burden of learning a new layout? So I got curious with the layouts that you've mentioned and I've found out that dextr keyboard is the one who stands out because of it's alphabetic arrangement. Why does it stand out? it's simply because there's no need for you to find the keys, it is where you'd expect them to be at. Learning curve is also very minimal and it really adapts on what preferences you would like to have. For my fellow readers who would love to give it a try, you can download the beta version in Google Play