3 ms·

Can't access the article due to database error, but since we're discussing keyboard layout effectiveness for developers: If we were indeed limited by input, wh

Can't access the article due to database error, but since we're discussing keyboard layout effectiveness for developers: If we were indeed limited by input, why wouldn't this come up in discussions about languages like CoffeeScript (or even Python/APL) that save keystrokes to begin with? In the case of Coffee and Python, the keys saved are actually the hard-to-press symbols as well. And yet I've never heard the point come up. Perhaps this is more about our need to feel superior by adopting a routine of cargo-cult efficiency than anything else. In the broader view of productivity, optimising keyboard layouts is more like optimising memcpy() in C. While it may bear some results, it's rarely the actual bottleneck.

vanderZwan 13y ago
> since we're discussing keyboard layout effectiveness for developers. We're not, at least not in the way you think. > In the broader view of productivity, optimising keyboard layouts is more like optimising memcpy() in C. While it may bear some results, it's rarely the actual bottleneck. This article is a solution developed by a someone in response to his own RSI problem, optimised for writing English with minimal strain, and presumably tested based on "how much do my arms hurt." So it's a solution/optimisation to a different problem altogether (which may or may not be relevant to you.)
lelf 13y ago
Personally, I wonder why there's not many discussions about hacker's keyboard layout. Where at least ()+-=. are dedicated keys