If I recall, this version of VLC to which you refer is not technically a universal binary but, rather, has been precompiled for Windows. http://www.videolan.org/vlc/
I'm 21-years-old and typed in QWERTY for seven years starting at age 12, ultimately reaching 130+ words per minute. Rather than study for a test at uni two years ago, I decided to start learning DVORAK. For the rest of the semester lab reports were hard to write and after a week, I was a steady 40 wpm on Dvorak but my QWERTY speed dropped to about 50 wpm--after such a loss, there was no turning back! After four months exclusively on Dvorak I was at 90 wpm and by the half-year mark I was at 120 wpm.
As for people who compare switching back-and-forth between keylayouts to bilingualism, they either (a) do not speak from experience or (b) do not type fast on either layout. Occasionally switching back to QWERTY is a REAL PAIN. The only words I can type fast on QWERTY include the URL to my uni's webmail page, my first and last name (email login), and email password. I've found that I only reach tolerable QWERTY speeds if I'm going back to QWERTY on a daily basis. I also think it helps to use the EXACT SAME KEYBOARD IN THE EXACT SAME LOCATION to really rev up QWERTY rates quickly. Of course, the latter statement sounds like psychobabble, but my muscle memory seems to benefit from these constants.
If you haven't garnered these from DVORAK fan sites, here are some little tidbits:
* 'a' and 'm' are the only keys that are not moved between QWERTY and ANSI Dvorak (more on ANSI later...)
* the Dvorak home row includes aoeu ih htns - (spaces insert for readibilty)
* as an OS X user, I find Dvorak much more amenable to common keyboard shortucts. Quit is cmd+Q and Close Window is cmd+w, which makes for easy muscle-memorisation on a Powerbook keyboard with the keys physically rearranged for Dvorak (http://www.geocities.com/rjpoling/MacOS/dvorak/dv orak_powerbook.jpg [geocities.com])
As for ANSI mentioned above, here's the real doozey: August Dvorak initially proposed an alternate number-row layout in his book Typewriting Behavior (1936, I think?). Rather than 12345 67890, Dvorak liked 75319 02468 (again, spaces inserted for readability). In theory, I don't know how much this helps. In practice, it's kinda useful these days since the '@' character is easily accessed with the index finger. This alternate number layout was NOT included in the standard ANSI Dvorak layout, but keymap files may be easily modified by true fanatics. On OS X, I highly recommend Ukelele (http://www.sil.org/computing/catalog/show_softwar e.asp?id=94 [sil.org]). I'm two-weeks into learning the alternate layout and am finally getting good at it.
In sum, the Dvorak layout markedly reduces finger movement for standard English text (http://www.acm.vt.edu/~jmaxwell/dvorak/comparePag e.html [vt.edu]); it seems to not be so helpful to developers. If you type fast on QWERTY now, you'll lose a lot of it after learning Dvorak. You may be able to get good enough at QWERTY but it won't be soon after learning Dvorak and it won't be fast and your boss will look at you funny when you're hunting and pecking.
Hope this helps.
Jon
I'm 21-years-old and typed in QWERTY for seven years starting at age 12, ultimately reaching 130+ words per minute. Rather than study for a test at uni two years ago, I decided to start learning DVORAK. For the rest of the semester lab reports were hard to write and after a week, I was a steady 40 wpm on Dvorak but my QWERTY speed dropped to about 50 wpm--after such a loss, there was no turning back! After four months exclusively on Dvorak I was at 90 wpm and by the half-year mark I was at 120 wpm.
As for people who compare switching back-and-forth between keylayouts to bilingualism, they either (a) do not speak from experience or (b) do not type fast on either layout. Occasionally switching back to QWERTY is a REAL PAIN. The only words I can type fast on QWERTY include the URL to my uni's webmail page, my first and last name (email login), and email password. I've found that I only reach tolerable QWERTY speeds if I'm going back to QWERTY on a daily basis. I also think it helps to use the EXACT SAME KEYBOARD IN THE EXACT SAME LOCATION to really rev up QWERTY rates quickly. Of course, the latter statement sounds like psychobabble, but my muscle memory seems to benefit from these constants.
If you haven't garnered these from DVORAK fan sites, here are some little tidbits:
* 'a' and 'm' are the only keys that are not moved between QWERTY and ANSI Dvorak (more on ANSI later...)
* the Dvorak home row includes aoeu ih htns - (spaces insert for readibilty)
* as an OS X user, I find Dvorak much more amenable to common keyboard shortucts. Quit is cmd+Q and Close Window is cmd+w, which makes for easy muscle-memorisation on a Powerbook keyboard with the keys physically rearranged for Dvorak (http://www.geocities.com/rjpoling/MacOS/dvorak/dv orak_powerbook.jpg)
As for ANSI mentioned above, here's the real doozey: August Dvorak initially proposed an alternate number-row layout in his book Typewriting Behavior (1936, I think?). Rather than 12345 67890, Dvorak liked 75319 02468 (again, spaces inserted for readability). In theory, I don't know how much this helps. In practice, it's kinda useful these days since the '@' character is easily accessed with the index finger. This alternate number layout was NOT included in the standard ANSI Dvorak layout, but keymap files may be easily modified by true fanatics. On OS X, I highly recommend Ukelele (http://www.sil.org/computing/catalog/show_softwar e.asp?id=94). I'm two-weeks into learning the alternate layout and am finally getting good at it.
In sum, the Dvorak layout markedly reduces finger movement for standard English text (http://www.acm.vt.edu/~jmaxwell/dvorak/comparePag e.html); it seems to not be so helpful to developers. If you type fast on QWERTY now, you'll lose a lot of it after learning Dvorak. You may be able to get good enough at QWERTY but it won't be soon after learning Dvorak and it won't be fast and your boss will look at you funny when you're hunting and pecking.
Slashdot Mirror
If I recall, this version of VLC to which you refer is not technically a universal binary but, rather, has been precompiled for Windows. http://www.videolan.org/vlc/
I'm 21-years-old and typed in QWERTY for seven years starting at age 12, ultimately reaching 130+ words per minute. Rather than study for a test at uni two years ago, I decided to start learning DVORAK. For the rest of the semester lab reports were hard to write and after a week, I was a steady 40 wpm on Dvorak but my QWERTY speed dropped to about 50 wpm--after such a loss, there was no turning back! After four months exclusively on Dvorak I was at 90 wpm and by the half-year mark I was at 120 wpm. As for people who compare switching back-and-forth between keylayouts to bilingualism, they either (a) do not speak from experience or (b) do not type fast on either layout. Occasionally switching back to QWERTY is a REAL PAIN. The only words I can type fast on QWERTY include the URL to my uni's webmail page, my first and last name (email login), and email password. I've found that I only reach tolerable QWERTY speeds if I'm going back to QWERTY on a daily basis. I also think it helps to use the EXACT SAME KEYBOARD IN THE EXACT SAME LOCATION to really rev up QWERTY rates quickly. Of course, the latter statement sounds like psychobabble, but my muscle memory seems to benefit from these constants. If you haven't garnered these from DVORAK fan sites, here are some little tidbits: * 'a' and 'm' are the only keys that are not moved between QWERTY and ANSI Dvorak (more on ANSI later...) * the Dvorak home row includes aoeu ih htns - (spaces insert for readibilty) * as an OS X user, I find Dvorak much more amenable to common keyboard shortucts. Quit is cmd+Q and Close Window is cmd+w, which makes for easy muscle-memorisation on a Powerbook keyboard with the keys physically rearranged for Dvorak (http://www.geocities.com/rjpoling/MacOS/dvorak/dv orak_powerbook.jpg [geocities.com])
As for ANSI mentioned above, here's the real doozey: August Dvorak initially proposed an alternate number-row layout in his book Typewriting Behavior (1936, I think?). Rather than 12345 67890, Dvorak liked 75319 02468 (again, spaces inserted for readability). In theory, I don't know how much this helps. In practice, it's kinda useful these days since the '@' character is easily accessed with the index finger. This alternate number layout was NOT included in the standard ANSI Dvorak layout, but keymap files may be easily modified by true fanatics. On OS X, I highly recommend Ukelele (http://www.sil.org/computing/catalog/show_softwar e.asp?id=94 [sil.org]). I'm two-weeks into learning the alternate layout and am finally getting good at it.
In sum, the Dvorak layout markedly reduces finger movement for standard English text (http://www.acm.vt.edu/~jmaxwell/dvorak/comparePag e.html [vt.edu]); it seems to not be so helpful to developers. If you type fast on QWERTY now, you'll lose a lot of it after learning Dvorak. You may be able to get good enough at QWERTY but it won't be soon after learning Dvorak and it won't be fast and your boss will look at you funny when you're hunting and pecking.
Hope this helps.
Jon
Wooo!
I'm 21-years-old and typed in QWERTY for seven years starting at age 12, ultimately reaching 130+ words per minute. Rather than study for a test at uni two years ago, I decided to start learning DVORAK. For the rest of the semester lab reports were hard to write and after a week, I was a steady 40 wpm on Dvorak but my QWERTY speed dropped to about 50 wpm--after such a loss, there was no turning back! After four months exclusively on Dvorak I was at 90 wpm and by the half-year mark I was at 120 wpm.
v orak_powerbook.jpg)
r e.asp?id=94). I'm two-weeks into learning the alternate layout and am finally getting good at it.
g e.html); it seems to not be so helpful to developers. If you type fast on QWERTY now, you'll lose a lot of it after learning Dvorak. You may be able to get good enough at QWERTY but it won't be soon after learning Dvorak and it won't be fast and your boss will look at you funny when you're hunting and pecking.
As for people who compare switching back-and-forth between keylayouts to bilingualism, they either (a) do not speak from experience or (b) do not type fast on either layout. Occasionally switching back to QWERTY is a REAL PAIN. The only words I can type fast on QWERTY include the URL to my uni's webmail page, my first and last name (email login), and email password. I've found that I only reach tolerable QWERTY speeds if I'm going back to QWERTY on a daily basis. I also think it helps to use the EXACT SAME KEYBOARD IN THE EXACT SAME LOCATION to really rev up QWERTY rates quickly. Of course, the latter statement sounds like psychobabble, but my muscle memory seems to benefit from these constants.
If you haven't garnered these from DVORAK fan sites, here are some little tidbits:
* 'a' and 'm' are the only keys that are not moved between QWERTY and ANSI Dvorak (more on ANSI later...)
* the Dvorak home row includes aoeu ih htns - (spaces insert for readibilty)
* as an OS X user, I find Dvorak much more amenable to common keyboard shortucts. Quit is cmd+Q and Close Window is cmd+w, which makes for easy muscle-memorisation on a Powerbook keyboard with the keys physically rearranged for Dvorak (http://www.geocities.com/rjpoling/MacOS/dvorak/d
As for ANSI mentioned above, here's the real doozey: August Dvorak initially proposed an alternate number-row layout in his book Typewriting Behavior (1936, I think?). Rather than 12345 67890, Dvorak liked 75319 02468 (again, spaces inserted for readability). In theory, I don't know how much this helps. In practice, it's kinda useful these days since the '@' character is easily accessed with the index finger. This alternate number layout was NOT included in the standard ANSI Dvorak layout, but keymap files may be easily modified by true fanatics. On OS X, I highly recommend Ukelele (http://www.sil.org/computing/catalog/show_softwa
In sum, the Dvorak layout markedly reduces finger movement for standard English text (http://www.acm.vt.edu/~jmaxwell/dvorak/comparePa
Hope this helps.
Jon