[jjoonathan]

It's ridiculous to claim that Simplified Dvorak is bad for programming while completely ignoring Programmer's Dvorak. Of course Simplified is worse at typing symbols, which is why anyone who cares about rapidly typing symbols will use Programmer's. But who are these programmers limited by typing speed? I've certainly never met one.

I don't take issue with the tests showing that Dvorak doesn't have speed benefits. My anecdata confirms this claim at the skill level which is relevant to me: my Dvorak typing speed, which I have made no effort to improve, is roughly the same as my QWERTY typing speed, which I also made no effort to improve.

However, Dvorak dramatically (factor of 2-3) decreases the fingertip slew distance which is monotonic in the distance your tendons will have to travel in your carpal tunnels for any given piece of typing. The difference isn't remotely subtle because it's easy to feel the tendons moving in your hand if you pay attention. In practice, it's the difference between tingles and numbness after 5 pages vs 15 pages of typing. So I do take issue with your claim that Dvorak is bad for carpal tunnel.

Your original post mentioned carpal tunnel and did not mention typing speed so I think it's more than fair to ask you to elaborate specifically on your claim regarding carpal tunnel.

[sparkie]

My typing speed with Dvorak is around the same as with QWERTY too, perhaps because I've not been using it for as many years. It took me 3 months to get up to speed (contrary to Wikipedia's claim of a year), and it's pretty easy to make the context switch between QWERTY and Dvorak - where I only make mistakes in the first few minutes of switching - and not six to eight weeks as Wikipedia suggests.

I didn't learn Dvorak to increase my typing speed - I learned because I was developing RSI in my right hand and put it down to QWERTY (and the mouse). The benefits of Dvorak are pretty clear when typing up large texts, although pain is still present after a few hours of typing. I found ergonomic keyboards to be a better solution than changing keyboard layout for dealing with RSI though, and I typically use QWERTY these days because configuring application's keybindings for dvorak is too awkward, and the gains are too little.

I've been considering learning Workman or QGMLWY, as their supposed benefits are even greater than Dvorak, and they have CUA-shortcut friendly layouts.

[zak_mc_kracken]

Programmer's Dvorak? This is the first time it's come up in the discussion, we were talking about the regular Dvorak keyboard.

There's hardly any information about Programmer's Dvorak, by the way, not even a Wikipedia page.

[jjoonathan]

> we were talking about the regular Dvorak keyboard

"This car sucks! It can't even reach freeway speeds!"

"If you would shift out of first gear, you could reach freeway speeds."

"We weren't talking about higher gears!"

> There's hardly any information about Programmer's Dvorak

It's a more recent layout, yes, but it has achieved decent enough penetration that I would expect anyone seriously contemplating the switch after 2010 or so to be aware of it. Anyone who looked at stack overflow opinions on Dvorak, selected a Dvorak layout on linux, or googled Dvorak and programming in conjunction would have run across it.

You still haven't substantiated your claim regarding carpal tunnel.

[fractallyte]

My own "programmer's Dvorak" is just regular Dvorak with a few keys remapped for my preferred language(s). Since the syntax is so minimal, it's works very well - for me.

(On Linux, it's a simple xmodmap configuration in /etc/X11. I even made a Windows equivalent: an executable that can be installed/removed like any other program.)

With so many keyboard customization utilities available, I'm surprised more folks don't optimize the keyboard for their own use. Kinda like building one's own lightsaber...

[coldtea]

Obviously the plain Dvorak keyboard is "no true Dvorak".