Slashdot Mirror
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?
Slashdot had an article a long time ago about going beyond the efficiency of Dvorak and determining what is better through genetic algorithms. You can read the Slashdot article here.
And no, I'm not saying this because I'm some some raving Dvorak promoter -- as people have pointed out, it isn't that much faster, and there is always the inconvenience for other people who want to use my computer (It's very simple to remap the keys back & forth with an international layout tool, but some people still can't get over the fact that all the keycaps have been swapped around). Dvorak just has that same geek fun factor that Linux does -- I like using something different from "everyone else" -- because I can -- even if it's only marginally better.
The last time I wanted to switch to Dvorak, many years ago in college when one does things like that, I went all out. Switched keyboard layouts, actually physically swapped the keys on the keyboard, etc.
The problem is that some programs used command-keys that were based on keyboard position, and some were based on actual letter (so command-o on the dvorak layout might be either command-o, because they were using the letter, or command-s, because that is the key in the same space on the qwerty layout). So I never knew from program to program which keyboard shortcut I'd be using.
It might not be as much of an issue now, with a more modern OS. On the other hand, now I really don't care.
=Brian
---
There is nothing so good that someone, somewhere, will not hate it.
Quay is typable with only the left hand on a Dvorak keyboard. So is pope, pupae, pike, and (probably) others. Note that the calculator on that page is not very good - it is unable to say 100% for "same hand". Try typing the word "i" for an example. I'm not saying whether QWERTY is better, just that your facts are wrong.
Trees can't go dancing
So do them a big favor
Pretend dancing stinks!
Actually, alphabetical order doesn't work much better for PDAs than QWERTY, a 6x5 square provides only an 8% speed increase over the traditional QWERTY layout, although I don't think this is quite the same layout as you were talking about.
The current most theoretically efficient method discovered is what's known as the "Metropolis II" layout after the algorithm used to design it (I'd offer you a link to it, but you need to be an ACM subscriber to get at the paper, and as far as I know tyhe keyboard layout itself has never been made publically available for use)
However, as mentioned, people's familiarity with the QWERTY layout is why it keeps getting put on there even if it's no longer the optimal layout, which means that when a user sits down at a new device they get faster immediate interaction rates if the keyboard is QWERTY due to familiarity with the letters as opposed to learning a new interaction method. (Although this deals only with PDA keyboards, here's a paper that comes to this conclusion.)
Yes, I'm getting off topic now, but I need to find a way to spout off all this extraneous knowledge I've picked up over time.
"I won't mod you down - I feel the need to call you a twit explicitly, rather than by implication."
From my experience, some people's parents were cheap :(. You can't have an effective war with one transformer, but you could take the same money and get a dozen gobots and have a righteous galactic battle.
I grew up using QWERTY. Although as I started typing at a very young age, I never learnt how to touch type.
I could type in QWERTY at adequate speeds, and I didn't feel I needed to be any faster.
The main drive for me to switch, was that I wanted to learn how to touch type. I'd tried to learn to touch type a few times, but it was always so easy to cheat and go back to typing with the incorrect fingures, as I was too used to typing in my own way.
I switched to DVORAK at work, and used QWERTY at home. For a number of years I could adequately use both. But it was not until I switched over at home as well that I really started becoming FAST at DVORAK.
At the moment, I use DVORAK everywhere, and have trouble with switching to QWERTY, although once I realise what's going on I can type by looking at the keys, reasonably well. I get the odd letter wrong, and if I try to think about it, I get REALLY confused.
One of the main drawbacks to using DVORAK is when programs (especially games) assume you have a QWERTY keyboard. Setting the regonal settings to DVORAK under windows is ok, but when games do their own keyboard mapping, they don't seem to expect you use anything other than QWERTY. One of the worst examples of this has got to be Counter Strike. The Half-life bit of it, when you are setting up all your keys, seems to be fine with your regonal settings set to DVORAK. As soon as you launch the game, it assumes you are in QWERTY. There is no way to set up your keys in QWERTY at all. It took me AGES to try and get the keys set up, cause I had to type in DVORAK where the QWERTY keys would be.
Also, as with any keyboard layout, getting it set up for the default in windows logon was a bitch, and I ended up hacking the registry until it magically worked.
The best solution may be to get something like at dvortyboard.com where you can switch between QWERTY and DVORAK in hardware as much as you like.
All in all though, I think the switch to DVORAK was well worth it. Speed isn't the main concern, although I am typing faster and more evenly with DVORAK. And I love typing now for some reason, as all of my fingers are used all the time.
I read alot of debates over how DVORAK being better is just a myth, and QWERTY is better yada yada yada. For me, I find DVORAK comfortable. The common letters are easy to reach without moving your left hand too much (I'm right handed, so moving my right hand is more comfortable and coordinated than moving my left hand) and I don't need to move my less coordinated (ring and pinky) fingers up and down much. QWERTY has jkl; in the home row of your main hand. Yet you surely don't use these keys much at all... Seems strange to me....
Verne.
There are only two things in this world that smell like fish. And one of them's fish...
I can think a lot faster than 70wpm.
Oh, bullshit. Ever sat and watched a rocket-hot typist compose at the keyboard? Typing under those circumstances is very bursty.
I have no idea how fast I type in words-per-minute, but I know that it's quite fast. When I'm on a roll, I can really get going. I write for a living. I average between 1,000 and 2,500 words of final copy per day. Total. Do you think my limiting factor is my typing speed?
Nobody, but NOBODY, who actually composes at the keyboard (as opposed to typing from a manuscript or something) is hampered in their productivity by how fast they can type. It simply doesn't work that way.
Oh, bullshit.
I don't know what kind of dream world you live in, but I have never in my life met a coder who could compose code faster than they could type it.
As someone who codes for a living, I'm not afraid to admit that I have often spent hours tracking down a bug which ends up being fixed with a one-line change. Typing speed isn't all that important unless you spend most of your day typing, and I've never met a coder who does.
Of course, I'm writing this comment on a Palm Tungsten C, which is pretty ironic (hint: tough to type fast on these itty-bitty keyboards).
ZFS: because love is never having to say fsck
What an annoying assumption. John C. Dvorak didn't come up with this keyboard layout. It was devised by Drs. August Dvorak and William Dealey in the 1930's. You can read more here
The current most theoretically efficient method discovered is what's known as the "Metropolis II" layout after the algorithm used to design it (I'd offer you a link to it, but you need to be an ACM subscriber to get at the paper, and as far as I know tyhe keyboard layout itself has never been made publically available for use)
You mean this?
If you're a zombie and you know it, bite your friend!