Live data from Hacker News

Workman Keyboard layout

viralintrospection.wordpress.com

81–90 of 128 posts

Re: Workman Keyboard layout

#81

20 years ago or so, I ran an evolutionary algorithm that permuted keys in a layout, evaluated them against a corpus of English texts from Project Gutenberg and the Linux kernel sources, and a home-grown cost function that penalized finger motion and especially double-hits by the same finger. The best layouts all had the property that the vowels were on the home row under the left hand, and the common consonants were…

CarpalX has a rather thorough exploration of this sort of thing: http://mkweb.bcgsc.ca/carpalx/

Re: Workman Keyboard layout

#82
post #76

Earlier quoted context omitted.

Never used it, but it sure had its fans. Too bad that it lies beneath the left hand.

I doubt that handedness really matters for these kind of tasks, but of course everyone has their preferences.

My left hand is clumsy, at least in comparison to my right hand. If commonly-used functions have to all be under one hand, left is bad for me.

Re: Workman Keyboard layout

#83
post #80

Earlier quoted context omitted.

The benefits of switching from the painful Sholes (QWERTY) layout to anything designed for comfort are huge. The benefits of switching between comfortable layouts are less than the cost of entry, at least for me.

> The benefits of switching from the painful Sholes (QWERTY) layout to anything designed for comfort are huge. Are there really? I find relevant studies lacking, not to mention this: https://www.utdallas.edu/~liebowit/keys1.html Also the whole DVORAK vs QWERTY thing presupposes we are all 20th century secretaries or novel writers and english at that, when in reality, we as programmers: 1) Have different patterns than…

I'm glad to see skepticism on this claim, and I don't have any good modern UX studies to point to. Anecdotally, I was going home with scary numbness on the backs of my hands and fingers at the ends of days of heavy shell interaction, despite touch-typing. Switching to Dvorak's layout cleared that problem up immediately and it hasn't returned in 24 years.

Re: Workman Keyboard layout

#84
> I went ahead and tried it out and soon enough after doing “ls -latr” on the terminal, I had to shake my head and sadly walk away from it. I didnt like the way Dvorak was laid out especially for the weak fingers of the right hand.

Of course it's going to feel awkward. The name "ls" was picked because it was easy to type on qwerty keyboards. Many Dvorak users get around this issue by creating an alias.

The author then shows off some metrics attesting to the superiority of his keyboard layout. The stats are put in a ridiculous light. A 2.3% reduction in finger travel is touted as "69,600 cm" or "34,000 less keystrokes".

Keyboard layouts are full of trade-offs. I don't know if the author realizes which trade-offs he's made, but it looks to me that he's optimized for finger travel distance at the expense of overall comfort and typing speed. Let me explain.

Compared to Colemak and Dvorak, the Workman layout reduces hand alternation. The idea behind hand alternation is to maximize typing speed. A finger on the left hand can strike a key while the right hand moves into position for the next key. If a keyboard layout doesn't encourage hand alternation, then one hand will sit idle while the other types multiple letters. Unless the letters are a rollover combo, such one-handed typing will be slower. Also: Compared to Colemak and Dvorak, the Workman layout increases keystrokes on the bottom row. The more you have to use the bottom row, the slower and less comfortable typing becomes.

Lastly, the improvements are negligible. Workman is 2-5% better than Dvorak and Colemak in the metrics that the author strove to optimize. If there are any important metrics that he didn't consider (and I think that's the case), his layout is almost certainly not better.

The lesson to draw from all this is: Use whatever keyboard layout you like, with the exception of qwerty. Qwerty is objectively terrible.

Re: Workman Keyboard layout

#85
post #79

Earlier quoted context omitted.

Hey, I found my best evolved layout: K,UYP WLMFC OAEID RNTHS Q.';Z XVGBJ Some things to note: 1) E and T just have to be under the middle fingers on the home row in any comfortable layout. 2) T and H need to be adjacent. 3) Vowels on one side, consonants on the other side of the home row. Keep the home row's Scrabble score to a minimum. Honestly, I think that's all that really matters. Dvorak isn't perfect for me (I/…

Hey, I did something similar about 12 years ago! I'd tried the Dvorak keyboard layout and found that I liked the guiding design principles, but decided that the actual layout was a sub-optimal implementation of those design principles. So, I dumped several megs of personal email archives (with the headers & '>' removed) and several megs of C++/Python source code (including comments) through some little statistical nu…

FWIW, I alias 'a' in the shell so that it cd's into directories but fires up my editor on regular files.

Coworker once said "dude, you only use one command".

Re: Workman Keyboard layout

#86
post #65

Using classic English language literature from a hundred years ago when advertising the keyboard for programmers is faulty thinking in my opinion. Why not use code for your testing? There is Programmer Dvorak, which solvea the right hand's excessive use. Though the numbers do get funky.

It's pretty unusual for me to just stream C++ code directly. Even when I know what I'm going to write, it doesn't come off my fingers in serial order. So for programming, I need good placement of editing commands, not characters for text entry. It's the other way around for natural language in comments, e-mail, blog posts, etc.

C/C++ no,but it's not uncommon for me to stream of consciousness sizable blocks of Javascript or of HTML plus templating language special characters.

Re: Workman Keyboard layout

#87
post #79

Earlier quoted context omitted.

Hey, I did something similar about 12 years ago! I'd tried the Dvorak keyboard layout and found that I liked the guiding design principles, but decided that the actual layout was a sub-optimal implementation of those design principles. So, I dumped several megs of personal email archives (with the headers & '>' removed) and several megs of C++/Python source code (including comments) through some little statistical nu…

FWIW, I alias 'a' in the shell so that it cd's into directories but fires up my editor on regular files. Coworker once said "dude, you only use one command".

[deleted]

Re: Workman Keyboard layout

#89
post #40

Also note the White Keyboard Layout, which was released recently as a reaction to the Workman layout due to some concerns about the optimizaiton parameters. https://github.com/mw8/white_keyboard_layout He defined a somewhat different set of scoring, then ran a simulated annealing algorithm to find a layout that optimized that score, then did a few manual tweaks for consistency and learnability. The code for the optim…

Even if you're not interested in switching keyboard layout, the writeup alone is well worth a read. THanks.
Post reply on HN