When comparing Carpalx QGMLWB vs Norman, the Slant community recommends Norman for most people. In the question“What are the best keyboard layouts for programming?” Norman is ranked 7th while Carpalx QGMLWB is ranked 11th. The most important reason people chose Norman is:
Norman keeps 22/26 letters in their original QWERTY finger, making the transition easier, and, according to many tests, does so without much loss in ergonomics.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Punctuation is in the same location as QWERTY
If you already know QWERTY you don't have to relearn the punctuation, with the single exception of the ;:
key which is in QWERTY's P
position, like Colemak.
Pro ZXC don't move compared to QWERTY
Like Colemak, the common undo, cut and copy Ctrl-commands don't move from their QWERTY positions. The V
(paste) key does though.
Pro Uses a colemak-like character layout
Uses the colemak character layout of moving P on a standard QWERTY keyboard layout one step down, extending the home row.
Pro Has low consecutive finger use
See the source here.
Pro Letter positions optimized
Via a quantitative effort model.
Pro Uses the same fingers as QWERTY for most letters
Norman keeps 22/26 letters in their original QWERTY finger, making the transition easier, and, according to many tests, does so without much loss in ergonomics.
Pro Keeps many common QWERTY shortcuts intact
Common shortcuts, such as ctrl + z, ctrl + x, etc., are kept in their original positions without much loss in ergonomics, making the transition easier.
Pro Feels fast and comfy
Pro Focuses on the keys easiest to reach for the human hand
Like Workman, Norman takes human anatomy into account.
Pro Designed using normal keyboards in mind
Unlike keyboard layouts such as workman that are desgined to be used by matrix keyboards, norman is made to be used by a standard keyboard.
Pro Favours the right hand
Unlike other layouts, such as workman, norman favours the right hand due to it usually being stronger than the left.
Cons
Con Effort model is speculative
The quantitative effort model central to the optimization is based on armchair speculation, rather than a scientific biomedical study. The chosen metrics and weighting for them are likely partially correct. But no-one is really sure how correct.
Con Doesn't take finger length into account
Unlike layouts such as norman and workman, QGMLWB doesn't take the length of fingers into account, for example on a standard QWERTY layout, it's easier to reach E than C.
Con Punctuation is not optimized
Programmers have to use punctuation a lot, but (except for the ;:
key, like Colemak) punctuation hasn't been moved from their positions on QWERTY. In fact, the non-letter characters , . - " _ ' ) ( ; 0 1 = 2 :
are used more than the least-frequent letter z
in a reasonable English corpus. Not optimizing punctuation at all, especially for programmers, is nonsense.
Con V key has moved compared to QWERTY
The common paste shortcut used in for example windows has been moved to the right hand, making the layout harder to learn. This however is fixed in the QGMLWY variant of the carpalx series.
Con A very small user base and community
Con Doesn't favor the right hand
For right handed users, this keyboard layout doesn't use the usually stronger right hand more than the left, infact it sometimes favors the left hand more.
Con Bad on SFBs
Lots of same finger bigrams (when 2 keys are hit simultaneously by one finger like the qwerty "ed".
Con A very small user base and community
Con Designed for right handed use
The Norman was designed with right handed use in mind, making it a less attractive choice for left handed users. However, tests done by some users (can be found in the comments) suggests that the Norman layout might be balanced.
Con Scores worse in ergonomics using the Carpalx test
Norman, although scoring better in travel distance, generally scores worse in the Carpalx test than layouts such as Colemak. See the source here.
