4 ms·
> 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, op
by 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.)