all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: James Harkins < jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-meta-return
Date: Sat, 23 Feb 2013 03:30:54 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130223T040538-679@post.gmane.org> (raw)
In-Reply-To: CAMgvimGhY2cy+5SwAoAGn+4erK9q0U2Vk41hGbX7c_9hHgwMzw@mail.gmail.com

42 147 <aeuster <at> gmail.com> writes:

> [continues off-topic]
>> Have you tried a Dvorak keyboard?
> A friend of mine ridicules me for being a QWERTY typist, but I have found no 
empirical evidence that it is actually superior. At best, it has been
> proven, in /some/ studies, to be /slightly/ superior; and from a cost-benefit 
standpoint, /slight/ superiority according to /some/ studies (and I should add, 
only at extreme speeds), is not worth relearning how to type.

FWIW, and I'm well aware this is purely anecdotal evidence with a sample size of 
1, after I switched to Dvorak some years ago, the difference in the amount of 
strain and fatigue I felt in my fingers and wrists was (and still is) more than 
slight. I know it's still the case because I have my customized Dvorak layout in 
Linux (it's basically a mirror image, but slightly different from left-handed 
Dvorak), but I never figured out how to replicate it in Windows 7. I don't have 
to use win7 often, just for teaching some Windows-only software, so it hasn't 
been worth digging through Microsoft documents. I've actually gotten a fair 
amount of QWERTY speed back, but boy, I can sure feel how much more *work* it 
is. The muscle movements flow in Dvorak, and they don't in QWERTY (not 
surprising, since QWERTY's purpose was to slow typists down and prevent the 
machinery from jamming).

I can believe that studies would find only a slight /speed/ improvement, but we 
aren't talking about speed. We're talking about RSI pain. I'd at least question 
the relevance of words/minute studies to measure reduction in muscle effort. 
Studies of finger travel are more on point.

The cost of relearning to type is high, but the cost is temporary and the 
benefits last the rest of your life.

Just my experience.
hjh

  reply	other threads:[~2013-02-23  3:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 19:32 org-meta-return 42 147
2013-02-20 19:40 ` org-meta-return Suvayu Ali
2013-02-20 21:17   ` org-meta-return 42 147
2013-02-20 21:57     ` org-meta-return Jonathan Leech-Pepin
2013-02-20 22:33     ` org-meta-return Suvayu Ali
2013-02-20 22:59     ` org-meta-return Nick Dokos
2013-02-20 23:25       ` org-meta-return W. Greenhouse
2013-02-20 23:28       ` org-meta-return 42 147
2013-02-21  0:11         ` org-meta-return Nick Dokos
2013-02-21  0:43           ` org-meta-return Suvayu Ali
2013-02-21  1:10             ` org-meta-return Nick Dokos
2013-02-26  9:03               ` org-meta-return Eric S Fraga
2013-02-26 11:10                 ` org-meta-return Sebastien Vauban
2013-02-26 13:16                   ` org-meta-return Suvayu Ali
2013-02-26 15:54                   ` org-meta-return Eric S Fraga
2013-02-21 21:16           ` org-meta-return 42 147
2013-02-23  3:30             ` James Harkins [this message]
2013-03-02 20:43             ` org-meta-return Michael Brand
2013-03-02 23:59               ` org-meta-return 42 147
2013-03-03 10:08                 ` org-meta-return Michael Brand
2013-03-03 10:44               ` org-meta-return Eric Abrahamsen
  -- strict thread matches above, loose matches on Subject: below --
2016-10-31  0:16 org-meta-return 42 147
2016-10-31 11:10 ` org-meta-return Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20130223T040538-679@post.gmane.org \
    --to=jamshark70@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.