Why is Everyone Still Stuck in QWERTY?

theWrkncacnter asks: "I was recently giving some instructions over IRC to a long time QWERTY keyboard user who wanted to switch to the Dvorak layout, mostly because a good majority of the people in channel had made the switch and were all talking it up, myself included, about how our speeds had increased and how its much more comfortable. This made me think, why don't more people use the Dvorak layout? Searching around I found an older topic on the subject, but that didn't answer too many questions, as most people in the comment section seemed to think that Dvorak vs. QWERTY was a hardware issue, when it is really a matter simply changing the layout on your particular OS. I took the time to pry off and remap my powerbook keyboard's keys but I have no problem typing in Dvorak on a physically QWERTY mapped keyboard, and I know many others who don't have a problem doing so either. So given all of this, why don't more people switch? Is it that most people just can't be bothered to make the change, even when its more efficient and more comfortable?" Is it mostly due to the fact that most people learn to type first on QWERTY due to its popularity, and hence don't bother to learn anything else?

Comments

Who needs Dvorak?

[darkov]

I hunt and peck faster than I need. I can hit the keys with my index finger without looking and I'm not going to learn to touch type ever, although I type for a living.

Changing keyboard layouts would reduce my typing speed with no benefit. The fact is that most people can't think faster than they can type, and only a fractiion of the population need to type very fast and would benefit from a change to Dvorak.

A question for those who have switched...

[swillden]

How hard is it to jump between QWERTY and Dvorak layouts? I've thought many times about switching to Dvorak, and I'm pretty certain that I could be back up to speed in only a few months, but there's no way that I can be restricted to using *only* the Dvorak layout, so the ability to remain moderately productive on a QWERTY keyboard is a prerequisite.

So, how hard is it to jump back and forth? Is it like having two separate modes, each equally capable, or do the two sets of muscle memories stomp on each other? I've known people who spend enough time on telephone and adding machine keypads to develop excellent "touch-typing" skills on both, and they could bounce between them flawlessly, never missing a single stroke even at high speed, in spite of the different layouts. OTOH, there are fewer keys and more "environmental" clues to distinguish between them.

I notice that (spoken) languages often seem to create the same sort of "modality", whereby a person fluent in two languages can trivially jump between the two with little risk of accidentally mixing them. OTOH, I find that I have a strong tendency to mix keywords and syntax across multiple programming languages, particularly if I'm not using different development environments (my theory is that the different IDEs provide some context that helps).

So, how does it work?

Re:Two reasons

[Rick the Red]

I second that. If I'm going to learn something new, I'd rather learn to use a Twiddler, that way I can take it with me and use it wherever I go. I'm just waiting until I can afford both it and a PDA with a USB Host port (why doesn't the Zaurus include this?).

tried, failed

[c]

Back in university, my roomates and I had a go at leaning dvorak. In our case, the most compelling reason was reduced risk of RSI, not typing speed. As an added bonus, it was also an opportunity for me to learn proper touch typing (which I never did with Qwerty... still haven't).

We never pulled it off.

We got all our X11 keyboards remapped. We changed the keycaps on my PS/2. We downloaded some tutor apps from the net. We even spent quite a bit of time actually practicing. Results were promising... But then reality kicked in.

At university labs, I was routinely using about 5 different keyboards a day, some X, some tty. Remapping all of them wasn't an option, so I was trying to learn Dvorak while still blasting out assignments in Qwerty. Then there's situations during the transition from Qwerty to Dvorak where there's no feedback... Trying to enter a password on a keyboard with Dvorak keycaps but a Qwerty layout is, uh, hard.

What killed the whole thing, however, is that I'm a vi user. vi at the best of times can be a disaster for bad typists. Just trying to navigate via ijkl in vi on Dvorak is futile, much less handling complex ingrained key patterns like df' or 'ay}. After years of vi use, I've got these patterns burned into my fingers. Learning a new keyboard without learning a new editor at the same time won't happen.

Yet another problem is that too much emphasis is placed on the letters. C/C++ programmers need a good symbol layout too and we make at least as much use of the symbols as the letters. Dvorak is, I found, a bit weaker in the symbol layout than Qwerty. {}[];()= are, I think, the most commonly used C symbols... This choice of symbols and the convenient placement on Qwerty is probably not accidental.

c.