News for hackers. Stuff that matters.
Re:The T-34 keyboard layout by codethief on Monday June 07, 2021 @05:43PM (#27427450)
> Nothing special going on with the function keys. Having them on the same positions as numbers makes them easy to learn, which is important for me as I almost never use them.

Unfortunately, most manufacturers of ergonomic keyboards seem to think along the same lines, so they omit the corresponding hardware keys and argue that you could always put the function keys on another layer if you really need them. I, however, use my function keys hundreds of times a day (mainly to switch workspaces) and I do not want to have press an extra key every single time.

The key principle I follow with all my key bindings is this: The more often I use a certain functionality, the more accessible it needs to be, i.e. the less work (or, literally, input) it should require in order to avoid putting needless strain on my fingers and wrists. (I have suffered from RSI in the past.) In particular, oft-used commands[1] should be available through a single key (or a very short and accessible[0] key chord) if possible. Unfortunately, the most common set of key bindings (Vim/Emacs/IntelliJ/…) usually violate this principle.

Long story short, this is the single reason why I haven't bought an ErgoDox/keyboardio/… so far.

Also, I don't think it really matters whether personally one uses a key X or not. In my experience, you can never have enough keys! And you will find an application eventually – provided the key is in the right place ergonomically speaking, i.e. easy to reach.

[0]: The more often I use a key chord, the stronger the fingers should be that push the individual keys – e.g. the thumb, index and middle finger.

[1]: Commands, in turn, that are used only rarely should actually not be available through a key binding at all – no one remembers them and they only clutter the key binding space and cause confusion when you do (accidentally) hit those keys. Instead, those commands should be accessible through a searchable command palette. (Think Shift-Shift in IntelliJ.)

Re:The T-34 keyboard layout by Jenk on Monday June 07, 2021 @06:57PM (#27428374)
The entire purpose of these layouts is to reduce movement to keys you most use. If you really are using the F-keys hundreds of times a day then it very much is in your ergonomic interest to bring those keys closer to the home row to make accessing them easier than stretching out for them.

In your specific case I'd probably map the layer modifier key on one hand, then map the F-keys like a numpad on the other so there is no same-hand chording. Though I strongly suspect you aren't using all 12 keys and instead are using say the first 5 or 6 only.

Re:The T-34 keyboard layout by Symbiote on Tuesday June 08, 2021 @03:44AM (#27431664)
Function keys are often used in combination with the mouse, and with other modifier keys.

F3 is common for "Find Next", F5 for "Refresh". I don't want to use two hands for these.

IntelliJ has defined shortcuts for F10, Shift+F10, Ctrl+F10 and Ctrl+Shift+F10. Adding another modifier to all these isn't great.

Re:The T-34 keyboard layout by opan on Tuesday June 08, 2021 @06:03AM (#27432525)
>IntelliJ has defined shortcuts for F10, Shift+F10, Ctrl+F10 and Ctrl+Shift+F10. Adding another modifier to all these isn't great.

You're thinking small here. With QMK keyboard firmware, a single key can send shift-f10 or similar. I have a top layer key that acts as ctrl-super and also as a sticky key (I don't have to hold it) because I configured a bunch of key chords in Sway that start with those keys. Mainly focusing specific programs by appid or class. So, I'll hit that key and then b for browser, v for video (mpv), etc. You can even have keys that directly type out parentheses, no shift needed. The default layout for my keyboard had that for both parens and brackets. I found more useful things to put on those keys, though.

I use a Pinky4 which takes some stuff off the outer edges compared to a 60%, but has more on the inner edges, and so I stuck that key somewhere along the upper right edge of the left half. If I were using qwerty, it'd be near t and g keys.

In addition to being able to run QMK on a keyboard, you could also get a macropad, or just a second keyboard (maybe something small like a planck, could go above your main one), and have all sorts of specific binds like this. I would recommend layers instead for anything not used constantly, but a case can be made for both options. I have mouse keys in a separate layer, letting me hold a modifier with my thumb and then use something similar to an arrow key cluster to move my mouse. I even have all 4 scroll directions mapped, which lets me scroll horizontally, unlike my actual mouse.

Software on the computer really affects use-case I think. In qutebrowser (or firefox + tridactyl) I just hit r to refresh a page. I never miss easy access to f5. I can also copy a page's url with yy instead of doing a dance of ctrl-l and then ctrl-c. I can still hit f5 if I have to. Like if using an unusual program or another computer with my keyboard.

It sounds like due to your software choices, you use the function row a lot more than me. There are some larger split keyboards, but it's worth considering changing some of your behavior/software also.

Re:The T-34 keyboard layout by Jenk on Tuesday June 08, 2021 @05:40AM (#27432276)
Alternatively, you map the most common shortcuts you use to single keys on a new layer.

But whatever, you do you :)

Re:The T-34 keyboard layout by xupybd on Tuesday June 08, 2021 @05:49AM (#27432325)
How do you find memorizing these? I use an ergo dox as my daily but haven't got the hang of layers. Any advice to getting more out of them?

I'm also not sure how to use more layers without dedicating more keys to switch between layers?

Re:The T-34 keyboard layout by neurotrace on Tuesday June 08, 2021 @10:45AM (#27435848)
On memorizing: for me, it hasn't been difficult. Specialty layer switches are placed on keys that are difficult to press so I don't accidentally hit them. Additionally, since they're out of the way, it's easy to remember them because of the difficulty.

For more common layer switches, I extensively use dual-use keys. For example, if I tap "F" then I get the letter "f" but if I hold it, it switches to a vim-like layer. HJKL becomes arrow keys, Y becomes Ctrl+C, etc. The point is that you don't have to dedicate more keys to do layer switching. You can have the same key do different things depending on how it's used.

For me, memorizing has been easy due to incremental change. I didn't come up with my new layout on day one then stick to it forever. I'd find a frequent pain point, tweak the layout, and memorize the tweak. It's easy to remember 2 or 3 key changes at a time.

Re:The T-34 keyboard layout by Jenk on Tuesday June 08, 2021 @05:56AM (#27432396)
For general typing - I dedicate ~15 minutes a day on sites like monkeytype.com. I also completed the courses on typing.com when I first received my moonlander. Monkeytype also has settings to emulate a lot of the popular alternative layouts if you want to try any out.

For shortcuts - I just conciously accepted it takes time to learn. I'd say it was about a month before I stopped reaching for the old shortcuts and started to use the layered shortcuts.

It can also help force you into it by not having the old keys mapped - obviously this comes with judgement on a per key basis. I'm not asking you to unmap "A" - but unmapping/not-mapping the F-keys in their usual place coerces you into using your new mapping and you'll just get the muscle memory eventually.

Re:The T-34 keyboard layout by codethief on Tuesday June 08, 2021 @07:34AM (#27433735)
I would generally agree, but in this particular case I do not because:

1) I hit the function keys far less often than regular character keys and

2) I rarely press the function keys while typing text since, as I mentioned, I use them to switch workspaces. In particular, I often use them while my one hand is on my mouse (think drag & drop) and, as you say, same-hand chording is out of question.

Re:The T-34 keyboard layout by tremon on Tuesday June 08, 2021 @10:56AM (#27436012)
I played the piano when I grew up, same-hand chording is second nature to me. It's all about wrist movement though, never strain your phalanges. I same-hand chord most close combinations: Ctrl-W is 5-3, Ctrl-C is 5-2, Alt-W is 3-1, as is Alt-P on the right-hand side. But I use two-hand combinations for almost everything else because the right-hand Ctrl and both Shift keys aren't easy to reach with opened fingers. The Ctrl key on the left is only easy to reach for me because I touch it with the side of my hand, not the tip of my pinky.

I have looked at ergonomic keyboards before, and have the same reservations about the number of keys as you. I use the numpad a lot for data entry, and my previous favourite keyboard was a Logitech one that had an additional row above the numpad that contained keys for parentheses (without using shift), an equals sign and a second backspace key. I did seriously consider the Maltron L90 full-width keyboard, but I couldn't source it locally and the price was too steep for me to buy without testing it first.

Having something like that keyboard coupled with a programmable (QMK) controller would be an option I'd seriously consider though, even without a separate numpad.

Re:The T-34 keyboard layout by fomine3 on Tuesday June 08, 2021 @03:11AM (#27431485)
I use both depending on situation. There's no reason to avoid mapping a key combination function that already exist as a key. There's no strict reason to avoid adding key that can be done by key combination (but needs more vertical space, cost, and effort to build). I don't care vertical spaces much so I prefer to have dedicated function keys.
Re:The T-34 keyboard layout by chme on Tuesday June 08, 2021 @01:28AM (#27430938)
> Also, I don't think it really matters whether personally one uses a key X or not. In my experience, you can never have enough keys! And you will find an application eventually – provided the key is in the right place ergonomically speaking, i.e. easy to reach.

I do own a ErgoDox and UHK and like them. I use them with my custom layout. However I also agree with you fully, that you cannot have enough keys and I miss all the keys a standard layout offers.

I think needing many keys, and changing a layout to not need to move your hands so much are two different problems.

What is better, having to move your hand to difficult to reach keys, for functions that you only need occasionally, or having to remember how to navigate to the right, rarely used layer? I think the former.

You can still change the layout to have the frequently used keys close to your finger, but if you don't need so many layers to allow the keyboard to work in all kinds of applications, that is a win for me.

I don't really like the highly application specific layouts you get with keyboards, that are missing keys compared to the standard layout.

Re:The T-34 keyboard layout by codethief on Tuesday June 08, 2021 @07:43AM (#27433821)
Thank you for your comment! I couldn't agree with you more!
Re:The T-34 keyboard layout by Symbiote on Tuesday June 08, 2021 @03:50AM (#27431702)
I made [1] to index ergonomic keyboards with sufficiently many/few keys (depending on preference). The issue seems fairly divisive, many people have strong preferences one way or the other.

Setting it to a minimum of ~76-80 keys shows there really aren't many options.

[1] https://aposymbiont.github.io/split-keyboards/

Re:The T-34 keyboard layout by codethief on Tuesday June 08, 2021 @07:39AM (#27433792)
Very cool, thank you!
Re:The T-34 keyboard layout by neurotrace on Monday June 07, 2021 @06:30PM (#27428099)
> Long story short, this is the single reason why I haven't bought an ErgoDox/keyboardio/… so far.

I don't really understand this conclusion. The point of these programmable keyboards is you can make them as work-free as you need. If you hit your function keys all the time, you can make the number row produce a function key just by holding it for a little longer or do like what OP did and make number chords match a function key. Press 1+2 to get F1, 2+3 to get F2, etc.

I understand not wanting to use a layer for everything which is why I don't care for ultra minimalist boards like the T-34 or Plank but an Ergodox has plenty of keys for my uses.

Re:The T-34 keyboard layout by tablespoon on Tuesday June 08, 2021 @12:25AM (#27430633)
>> Long story short, this is the single reason why I haven't bought an ErgoDox/keyboardio/… so far.

> I don't really understand this conclusion. The point of these programmable keyboards is you can make them as work-free as you need. If you hit your function keys all the time, you can make the number row produce a function key just by holding it for a little longer or do like what OP did and make number chords match a function key. Press 1+2 to get F1, 2+3 to get F2, etc.

All those solutions are pretty sub-optimal if you actually use your F-keys regularly. Making a number stand in for an F-key after being held for a moment actually seems like it would be the most annoying workaround of all.

Re:The T-34 keyboard layout by whoisburbansky on Tuesday June 08, 2021 @01:00AM (#27430793)
Alternatively, if GP really uses function keys that often, maybe it makes sense to just have the number keys default to function keys instead, and only output numbers on long press.
Re:The T-34 keyboard layout by croh on Tuesday June 08, 2021 @02:49PM (#27439251)
I would like to know if you do touch type. Touch typing plays huge role in keyboard experience imo.

In my experience, linux has the most ergonomic shortcuts (combination of windows and mac - linux mint with cinnamon desktop) with little bit of customization. If you have a habit of not touching mouse much, honestly linux rocks.

Mac has few consistent keyboard shortcuts but you can't operate system without mouse/touchpad. And for many keyboard shortcuts, you need to press awakwardly 3-4 keys simultaneously.

Windows has some good shortcuts but it is not designed to use by keyboard soley. Focus seems more on mouse.

Also I would highly recommend mechanical keyboards. You can configure good amount of shortcuts using control key and press it using your palm.

Re:The T-34 keyboard layout by samatman on Tuesday June 08, 2021 @12:52AM (#27430764)
I type @, #, and especially () more than I could ever hit a function key.

Those are two-key characters. F2, F3, F9 and F10 are the same keys with a different modifier.

It's really not a big deal. ErgoDox is great (even if I'm still miffed my first one died two months out of warranty).

Re:The T-34 keyboard layout by rgoulter on Monday June 07, 2021 @10:05PM (#27429841)
It's a trade-off for hand-movement distance vs having to use modifiers.

e.g. to type (), you hold Shift then type 89. That's probably easier than needing an extra row of keys for symbols, even if you use the symbols frequently.

Re:The T-34 keyboard layout by codethief on Tuesday June 08, 2021 @07:48AM (#27433855)
> It's a trade-off for hand-movement distance vs having to use modifiers.

Yes, but in case of the function keys (which, as I said, I use to switch workspaces) I never press them while I'm writing text but rather before/after, so the distance my hands travel doesn't play much of a role.

Also, one-handed usage of these keys along with a mouse (think drag and drop) is important to me, which is another reason against resorting to a key chord.

Re:The T-34 keyboard layout by rgoulter on Wednesday June 09, 2021 @01:07AM (#27444418)
I mostly agree split keyboards aren't as good for one-handed usage where keys across the whole board are needed. Maybe for this usage something like the Kinesis Freestyle is more usable than a small keyboard like the Corne, but using the RHS will still suffer.

I don't think that makes the keyboards bad; it's just they're better suited to usages where you can use both hands at once compared to one-handed usage.

For "using function keys a lot", I don't think having the function keys behind a modifier is slower or inherently worse than having extra keys for it. - If you prefer to have the extra keys and don't mind moving your hand, that's fine. - But since many of these keyboards are designed with "minimize hand movement" in mind, it's coherent for the designs to omit the row of function keys (and even the row of number keys).

There are a handful of designs which prioritize number of keys over reducing hand movement. e.g. BFO9000 https://keeb.io/products/bfo-9000-keyboard-customizable-full...

Re:The T-34 keyboard layout by fouric on Monday June 07, 2021 @05:56PM (#27427610)
> In particular, oft-used commands[1] should be available through a single key (or a very short and accessible[0] key chord) if possible.

Wouldn't a real ergonomic keyboard (i.e. Dactyl-Manuform or Squeezebox) with thumb clusters fit this bill? Those put the modifier keys on your thumbs, so a two-key chord (layer mod + main key -> function key) should be relatively "short and accessible", at least by my standards.

Re:The T-34 keyboard layout by codethief on Tuesday June 08, 2021 @07:48AM (#27433859)
Unfortunately, it wouldn't, see my comment here -> https://news.ycombinator.com/item?id=27433855
Re:The T-34 keyboard layout by hsbauauvhabzb on Monday June 07, 2021 @06:25PM (#27428030)
If function keys switch workstations you’re either violating your own rule or don’t use workspaces enough.