Last week’s post on my arm ache (I’m not going to call it carpal tunnel, because I don’t actually know what it is, besides annoying and painful) spawned a side-conversation on the merits of the Dvorak keyboard layout. It turns out this is another Mac vs. PC or Xbox vs. PS3 issue:
- It’s totally better. Like, for sure.
- No way. Not better at all.
Great. Why are we still having this debate 72 years after the Dvorak layout was introduced? This disagreement over something easily quantified is kind of strange coming from the tech community. I can understand debates over acupuncture, herbal medicine, flavors of Linux, game consoles, and other things which have subjective quantities, differing user priorities, placebo effects, and multiple variables to be weighed. But when we’re talking about keyboard layouts we’re all comparing one quantity: Words Per Minute. It’s easily measured and not subject to user bias. Oh, this “feels” faster? You clock it on a stopwatch and look at the results. One study found no advantage, but it took existing professional typists and compared them after a couple of months. That’s not really reasonable or fair to take someone who’s been touch-typing QWERTY for a decade, give them a couple of months at Dvorak, and compare the speeds.
A real test would be to take two large groups of non-typists and teach one Qwerty and the other Dvorak. Every week we see little news tidbits about stupid studies (usually paid for by the government) that stun us with revelations like, “fat people eat more food than thin people” or “teenagers think about sex pretty often” or “unmarried men have more disposable income than same-age married couples with children”. We can find time to have scientists tell us the sky is blue, but in all these years nobody has ever sat down and really quantified the difference between Dvorak and QWERTY in a proper unbiased scientific study?
This wouldn’t, in and of itself, tell us if switching to Dvorak would be worth it for an individual or organization. That question is naturally going to be a fiendish one, but just having the WPM of QWERTY vs. Dvorak would go a long way to telling us if it was even worth thinking about.
The true story of three strange days in 1989, when the last months of my adolescence ran out and the first few sparks of adulthood appeared.
Programming Language for Games
Game developer Jon Blow is making a programming language just for games. Why is he doing this, and what will it mean for game development?
Trashing the Heap
What does it mean when a program crashes, and why does it happen?
Here is a 13 part series where I talk about programming games, programming languages, and programming problems.
id Software Coding Style
When the source code for Doom 3 was released, we got a look at some of the style conventions used by the developers. Here I analyze this style and explain what it all means.