Is DVORAK Gaining Traction Among Coders?
coderpath asks: "At a recent Seattle Ruby Brigade hack night someone asked how many people used the DVORAK keyboard layout. Out of 9 people, 7 used DVORAK and only 2 were using QWERTY. I personally made the switch last Christmas, after 25 years of typing with QWERTY. What do you use? Have you switched to DVORAK? Have you been wanting to make the switch? Has anyone else noticed an increase in adoption of DVORAK lately?"
Dvorak is optimized for writing English. Most coders - like most computer users in general - do not use English as their main language, and for us Dvorak is substantially worse than the qwerty layout in every way.
So no, most coders are not switching to Dvorak.
Trust the Computer. The Computer is your friend.
I don't know about that. If you already type about 100 wpm or so, how great is Dvorak giong to be for a coder? Are you really going to write code at 300 wpm? I doubt it. And while I suppose it might put less straight on your fingers, a lot of us have absolutely no problem with QWERTY. Not to mention the time involved in re-learning a new layout. And I gaurantee they aren't teaching Dvorak in school.
It's an improvement over QWERTY. Over that I don't think there is any doubt. But I'm not sure the improvement is worth it if what you have is working as it is. Dvorak is mostly just something people can brag about to be different, just like people who buy Zunes and iRivers so they can show how cool and different they are because they didn't buy an iPod.
DVORAK is another way to show other people that you're different. Any benefits are minuscule and are outweighed by the incompatibility downsides. It's another symptom of the "geek" disease.
The complaints about there not being many Dvorak keyboards for sale are just silly.
Why would you change layouts without bothering to learn how to touch-type??? If you don't touch-type, you will never type fast, regardless of which layout you use. It doesn't matter what the keys on your keyboard say if you are touch-typing.
The best thing to do when learning a new layout is to have a copy of it on paper taped to your monitor. You want to get out of the habit of looking at the keyboard, not perpetuate it.
I learnt VIM with Qwerty, and now I use VIM with Dvorak, a lot better and more skilfully than before. There's no reason to remap VIM's layout (and plenty of reasons not to). It will probably take a while to get used to it, but once you are you might find you use hjkl a lot more: in particular, I've found the hj (up/down ... or is it down/up? i just use them, i don't think about them) to be much better placed on dvorak than qwerty (they're on the left hand, so you have a choice: use hj with left hand, or cursor keys with right hand).
:)
Once you're used to VIM+dvorak, it's absolutely no harder than VIM+qwerty. I would expect it'll take you longer to get used to VIM+dvorak than anything else+dvorak, but if you love vi as much as I do, it'll only motivate you to learn faster
On the other hand: Although I can touchtype fluently in qwerty and dvorak, my VIM+qwerty skills are almost entirely gone. I have to stop and think about just about everything; it's painful and the only time I ever regret switching. If you're going to be bouncing around on computers whose keyboard layouts you can't control, and you use VIM, consider this before switching. Maybe just remap some keys so up/down are where god (not Bill Joy) intended.
Look out!
I switched to Dvorak. However:
1) I hated switching the hotkeys of every app I touched.
2) After a month was still significantly faster at QWERTY and doubted I could catch up to a lifetime of QWERTY in less than a year.
3) Knew the world would always be qwerty and I usually wouldn't be able to switch it over, so I would have to switch back and forth at work, on a co-workers computer, on my blackberry, etc etc etc.
so I gave up.
I'm not going to carry around a config file for the 10,000 applications I use every week on multiple computers because I want to type a bit faster. That's a false optimization in my opinion.