Love this site!! Thanks for linking! I considered making one like this but never had time. Always found it so hard to know whats been done in the mech keyboard area with so many home grown and low volume boards.
Thanks, and to the GP for posting it! It's my site.
I try and pay some attention to Reddit for new things, but it's more difficult to keep up with keyboards only available for a short time / no longer available.
I’d love an ultimate hacking keyboard, but honestly, the BT Mist Barroco MD770 is fine. And I guess I’d want larger market for consumer ergo keyboards and not just these specialised items that many people can’t afford.
a caveat about Freestyle2 - it is not ortholinear, meaning keys are staggered like most regular keyboards. Kinesis Advantage 2 on the other hand is split, concave, and ortholiner - highly recommend.
For rare occassions where a numpad is desired you could use a dedicated one. There is even an IPv6 calculator numpad. Which also works great for MAC addresses. There is no reason why you cannot have specific keybinds or maps for such a purpose though, except muscle memory / learning curve.
Cool idea, I appreciate the effort to make it affordable, and the wider spacing around the arrow keys. I do wonder why the shift key is regular key sized -- I find hitting it with the little finger requires more target space.
The best solution I've seen personally is my keyboard has a foot pedal, that when held changes some of the normal keys into a numpad. It's a kind of a mode switch. So no need to stretch extra distance or anything.
It's a bit much in terms of...someone had to implement this nonsense, and I had to buy the optional foot pedal. But if I'm honest, it's really nice.
Same, when I hold a thumb key my right hand turns into the numpad and my left hand is on a set of arrow keys, where s, d, f correspond to <-, \/, ->, and a, q, caps, tab change to control, alt, control+shift, alt+shift, respectively. I've tried to pick up Vim with this setup and always feel like my keyboard makes it irrelevant.
A good design puts the Numpad on the left (if right handed)
Primarily, this is because the mouse arm doesn't like being hyperextended to the right, resulting in shoulder issues down the line.
A quick look at this keeb immediately brings a few complaints to me. Primarily, the removal of the function key row always sticks out to me as an annoyance. Vertical space is most definitely not at a premium, as far as ergonomics go.
Not quite. The main issue here is the keyboard width and what it does to the angle of your mouse hand. Use of the mouse at angles too far from the forward axis of the body may result in shoulder issues down the line (At least that's what I've read, experienced, and was told by my physical therapist)
I also do this. I put a trackpad on the left, so I can let my right arm rest. Every few days I switch which hand is the trackpad hand. Track pads are easy to use left handed especially since programming is mostly scrolling and a few rare taps.
If you want a split keyboard for ergonomic reasons, a fantastic resource is [1]. It lets you compare sizes and shapes, and print out full-size paper mockups so you can try them on your hands.
I did this and it turned out the keyboard I thought I wanted was too large. I'm now planning to build a Kyria.
This thing seems so silly. If you're going to drop down to something like a Lily58, why is the nav cluster the thing you cling to? Why not add an extra row to bring in the f keys, and make it a full 75% board?
Disagree strongly. I spent about 6 months traveling with a 60% in my bag (1st gen touchbar keyboard is the absolute worst). I had it configured fairly typically (split spacebar but no arrow cluster). I had arrow clusters mapped to layer+wasd and layer+ijkl. It never became comfortable. My travel keyboard got upgraded to a 65%. Still use a kinesis advantage at home (it's just too big to pack for short trips). I've built a dactyl, I may start traveling with it instead (if I every have to go back to travel).
To be fair I'm a Vim user and so hjkl feels natural to me. I just also have to hold my right thumb down.
Not sure how others do it, but on standard keyboards I've always struggled with accurately moving my hands; for example one journey to the arrow cluster and back meant my right hand usually landed on the wrong row or column if I wasn't looking. All issues of that kind just disappeared when I started using a keyboard actually designed for human hands and reduced hand/wrist movement.
But the reason custom keyboards exist is exactly because different people want different things, and that's fine.
> Not sure how others do it, but on standard keyboards I've always struggled with accurately moving my hands
To the best of my memory, I just accurately moved my hands even as far as the \| or =/+ keys. Using arrow keys would've required quickly feeling for the arrow-key cluster before using it.
Now that I'm on a split keyboard with a reduced number of keys, I think people vastly discount how difficult/awkward it is to accurately use the standard keyboard layout for programming without looking at the keyboard.
I've built a similar keyboard myself but found the hardest part was to get the wrist rest and shape correctly. I went back to using an MS sculpt which isn't perfect, just more relaxing.
Think I might try a Keyboardio 100 when it comes out as it seems to have everything.
No F1-F12 keys? Maybe it is just a software I use all day (IntelliJ), but I think others also make some use of functional keys (for instance I like Windows convention that F2 is rename, whatever it means in a given context).
Your keyboard also doesn't have keys for {}, (), ?, ~ etc., yet you still manage to type them with a shift key.
Same thing here. This isn't even a very extreme case, 40% keyboards also don't have a numrow. Still just as quick to type on if you're used to it, with less hand movement. Definitely not everyone's cup of tea, though.
The issue I see with this is that the {} keys are usually just shift + []. Whereas the Fx keys are often pressed together with some combination of ctrl / alt / shift. So not having the row, that would add another key to the combo. Or make it a two-step process.
I actually have the same frustration as GP. I usually want a 75% keyboard so that I can have my mouse close to it, and since I don't ever use the numpad, that works out great.
But I don't care about the keyboard being actually small, so I would absolutely love some of those "macro keys" like on the gaming keyboards and also direct access to media keys.
Yes, I know you can have layers and combinations, and it might not even be that much slower (or at all) with one of those compact keyboards, but I find it much more comfortable to be able to only push one key with one finger.
I sometimes use my keyboards while doing something else besides "full-on typing" with both hands on the keys. Granted, in those cases I wouldn't be bothered by a full-width keyboard, but having two keyboards is just not something I'd consider practical.
F-Row on those layouts us mapped onto a layer at the number-row. It's good for blind-typing from homerow, but pretty poor for casual typing. I'm not always on homerow, in those moments typing an F-key is cumbersome with layers. It's also missing out on a full row of keys I could use for more exotic mappings, forcing me to use more complicated layers.
The typical mapping is much like a macbook these days. layer+numrow. It's a pretty easy one to digest (f11 under 0, f12 under -).
I don't go for '40' keyboards though. It's just too much overhead for too many keys, especially for software dev work. I wouldn't go smaller than '60' and don't myself go smaller than '65'.
It looks almost perfect: a trackball placed under one of the thumbs would make it possible to not have to use any mouse. Maybe add some foot pedals too.
69 comments
[ 3.0 ms ] story [ 236 ms ] threadI try and pay some attention to Reddit for new things, but it's more difficult to keep up with keyboards only available for a short time / no longer available.
Just about got one half all wired up... a hell of a project to jump into when you can't solder to save yourself :D
I've built my own keyboard but turns out I'm quite happy with the above Kinesis Freestyle.
I bought the optional VIP kit to add some tenting ability and I'm really happy with it for the price.
https://kinesis-ergo.com/shop/freestyle-pro/
There's a logo on there. I wonder if it's a sticker, or a custom package or something.
The logo on the MCU is the https://deskthority.net/wiki/Elite-C and it's silk screened on.
Ergonomic keyboards often dont have a numpad for a reason - I find that its the mouse that is more detrimental to my arm than the keyboard. By far.
The numpad is just a distance that I have to travel over when going from keyboard to mouse and vice versa.
Numpads are useless to me.
It's a bit much in terms of...someone had to implement this nonsense, and I had to buy the optional foot pedal. But if I'm honest, it's really nice.
I would use neither side, to allow tenting the two halves.
Primarily, this is because the mouse arm doesn't like being hyperextended to the right, resulting in shoulder issues down the line.
A quick look at this keeb immediately brings a few complaints to me. Primarily, the removal of the function key row always sticks out to me as an annoyance. Vertical space is most definitely not at a premium, as far as ergonomics go.
Even better is to mirror it so you can use your right hand's already cultivated muscle memory.
I have a separate numpad with a usb connection so I can put it wherever. Worth the $20.
I put my trackball to the left despite being right handed. Didn't take too long to adjust.
Put arrows and numbers on a layer and then you can just hold a modifier to access that layer without moving your hand.
I did this and it turned out the keyboard I thought I wanted was too large. I'm now planning to build a Kyria.
1. https://jhelvy.shinyapps.io/splitkbcompare/
Not sure how others do it, but on standard keyboards I've always struggled with accurately moving my hands; for example one journey to the arrow cluster and back meant my right hand usually landed on the wrong row or column if I wasn't looking. All issues of that kind just disappeared when I started using a keyboard actually designed for human hands and reduced hand/wrist movement.
But the reason custom keyboards exist is exactly because different people want different things, and that's fine.
To the best of my memory, I just accurately moved my hands even as far as the \| or =/+ keys. Using arrow keys would've required quickly feeling for the arrow-key cluster before using it.
Now that I'm on a split keyboard with a reduced number of keys, I think people vastly discount how difficult/awkward it is to accurately use the standard keyboard layout for programming without looking at the keyboard.
Think I might try a Keyboardio 100 when it comes out as it seems to have everything.
Same thing here. This isn't even a very extreme case, 40% keyboards also don't have a numrow. Still just as quick to type on if you're used to it, with less hand movement. Definitely not everyone's cup of tea, though.
I actually have the same frustration as GP. I usually want a 75% keyboard so that I can have my mouse close to it, and since I don't ever use the numpad, that works out great.
But I don't care about the keyboard being actually small, so I would absolutely love some of those "macro keys" like on the gaming keyboards and also direct access to media keys.
Yes, I know you can have layers and combinations, and it might not even be that much slower (or at all) with one of those compact keyboards, but I find it much more comfortable to be able to only push one key with one finger.
I sometimes use my keyboards while doing something else besides "full-on typing" with both hands on the keys. Granted, in those cases I wouldn't be bothered by a full-width keyboard, but having two keyboards is just not something I'd consider practical.
I configured it so pressing 1 and Q together¹ sends F1. I use this far more often than Fn+1, since I can do 1Q singlehanded/singlefingered.
¹ Actually 1 and ", because Dvorak.
I don't go for '40' keyboards though. It's just too much overhead for too many keys, especially for software dev work. I wouldn't go smaller than '60' and don't myself go smaller than '65'.
If you are just looking for additional keys or thumb modifiers I would go with a Japanese keyboard[1]. They are cheaper and very standardized.
[1]: https://www.amazon.com/ELECOM-Japanese-Wireless-Conformity-T...