8/11/2023 0 Comments Programmer dvorak keyboardAt least in the source code I write, the former is used over twice as frequent as the latter. This also gives some credibility to the idea of swapping ‘i’ and ‘u’ keys on Dvorak-based layouts. Since inevitably someone will be curious about comparison to Qwerty layout, the statistics for the letters are as follows: Letter Frequency Dvorak Qwerty e 11.5% home top t 9.1% home top* i 7.5% home* top a 7.2% home home n 7.0% home bottom* s 6.8% home home r 6.7% top top o 6.5% home top l 4.6% top home c 4.3% top bottom d 3.7% home* home p 3.1% top top u 3.1% home top m 2.9% bottom bottom h 2.9% home home* f 2.8% top* home g 2.1% top home* b 1.6% bottom* bottom* y 1.6% top* top* w 1.3% bottom top v 1.0% bottom bottom k 1.0% bottom home x 0.9% bottom* bottom z 0.4% bottom bottom j 0.3% bottom home q 0.2% bottom topĪsterisk indicates keys towards the middle of the keyboard which index finger needs to stretch sideways to reach. Overall though, I’m fairly satisfied with the results demonstrating that for me Programmer Dvorak was a better choice than regular Dvorak layout. It’s hard to tell whether that would affect the data though or whether the effect balances itself out. Looking at the files also ignores effects of copying and pasting text. For example, while I don’t configure my editor to automatically insert parenthesise, braces or apostrophes, if I had such feature enabled, methodology chosen here would overestimate use of punctuation characters. After all, looking at the characters in source files doesn’t necessary reflect what keys are pressed to construct those files. Who knows what catastrophes were averted thanks to me!Įxcept of course this was hardly scientific and the results should be taken with a grain of salt. It has been scientifically proven that Programmer Dvorak is better than regular Dvorak. Histogram of characters used in text files authored by me present in my Git repositories excluding Emacs Lisp files. Since letters are on the same position on both layouts in question, only digits and punctuation characters are compared on the histogram: Not number row Unshifted (number row) Shifted (number row) - ". To test this I’ve grabbed all my git repositories and constructed a histogram of characters used in text files present there. The hypothesis goes that developers use digits less often thus such design optimises the layout for them. The main differences between the two is that in the former digits are entered with Shift key pressed down which allows several punctuation marks often used when programming to be typed without the need to reach for Shift. I’m talking of course about the decision to learn Programmer Dvorak rather than a regular Dvorak keyboard layout. But did I make a wise choice? Or had I chosen poorly? Had I went a different path, the pl(dvp) layout might have never seen the light of day. Update: The article was updated in October 2021 to include direct comparison shift usage between Dvorak and Programmer Dvorak layouts.Ī few years age I’ve made a decision that had the potential to change the course of history.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |