Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Programming on 34 Keys

peppe.rs

Post reply on HN
Print view View original

61–70 of 71 posts

Re: Programming on 34 Keys

#61

Post by jhanschoo »

comfypotato wrote: post #57
alpaca128 wrote: post #45

Earlier quoted context omitted.

It's much more comfortable imho. You can reach all buttons without moving the hands all over the place, arrow keys are directly under my fingers at all times. It's not faster if you meant that with "efficient", but it certainly makes standard keyboards feel cumbersome to use. On the other hand more keys everywhere don't make you more efficient either, they just increase the chance of you messing up a hand movement wh…

For me, it’s the confidence of knowing you’re hitting the right key. Memorizing how your layers are configured is nbd (it quickly become second nature). 42 keys (CRKBD?) allows you to confidently strike each key and confidently return to home. I’ve never been able to guarantee this if a single key is even 2 units away from home. That being said, I think the most important thing is that you like what you’re using. If…

> Memorizing how your layers are configured is nbd

Ymmv; I have difficulty remembering the chords for keys I use once a week or once a month.

Re: Programming on 34 Keys

#63

Post by wtcactus »

This is interesting from an observational point of view, but I've went down that rabbit hole and it's a never ending one. In the end, my productivity didn't improve anywhere near the time I eternaly spent optimizing the method.

I went back using a simple ANSI US layout keyboard (not the standard here) where the only change I do is to assign CTRL to CAPS LOCK.

Re: Programming on 34 Keys

#64

Post by frosted-flakes »

jrockway wrote: post #40
shadowofneptune wrote: post #37

The given reason for going from 58 keys, then to 34, is ergononics. There has to be a better way to provide ergonomics than such a heavily shifted system, no? I'm not sure I could switch to a keyboard if it meant giving up QWERTY touch typing.

I find shifting extremely comfortable, but not quite to the extent as the author of this post. Like the author, I use thumb keys on the opposite hand to make the other hand start typing symbols. For example, I press the key below V with my left hand, and then home row on the right hand "jkl;" becomes "({})". (Actually, the whole side becomes symbols. I use the characters below the numbers to type the shifted symbol t…

Why don't you just Ctrl+Backspace instead of hammering the backspace key? Works fine on Windows, contrary to your last sentence.

Re: Programming on 34 Keys

#66

Post by nomel »

aidenn0 wrote: post #38
nomel wrote: post #36

When I see this much effort, it just makes me think that, at some point, maybe it's worth ditching the whole concept of giant buttons: https://www.charachorder.com/products/charachorder-one

I'm blanking on the name, but there was an older 5-way switch keyboard, where the 4 non-thumb fingers went in a recess with 4 paddles and a push-button; I've known several people who used that because of severe RSI, but it was quite expensive. [edit] Searching split keyboards on google image search for long enough found it: https://en.wikipedia.org/wiki/DataHand#/media/File:DataHand_...

Yes, this is actually what lead me to the CharaChorder! The data hand seems superior for single letter entry, but the CharaChorder has a type of chording built in to the firmware. I imagine sticking their chording engine in the DataHand would be incredible.

Re: Programming on 34 Keys

#67

Post by mcluck »

bayindirh wrote: post #53
600frogs wrote: post #51

I've fallen all the way down this rabbit hole - from a full-size to a 60% to an ergodox to a CRKBD (36 key split) - and come all the way out again, settling with a chiclet standard qwerty (Apple wireless keyboard). I think the central hypothesis of using these keyboards is flawed. It seems to all centre around thinking that less movement is better, and that keeping as close to the home row as possible is king, even i…

> Human bodies are meant to move. Most people don't understand it, or understand it too late, after they have joint pain. I concur with you on these extremely pared down keyboards. It's a nice and niche optimization for the use cases you have (programming in a certain language, etc.), however the general applicability of the tool dies with every iteration, plus the movement aspect of the body. I've moved to 75% keybo…

I actually moved to an ergodox _because_ of pain. Since moving to a split ergo board my back doesn't hurt and I've stopped getting tingling in my ulnar nerve. Different situations for different people, I suppose

Re: Programming on 34 Keys

#68

Post by comfypotato »

jhanschoo wrote: post #61
comfypotato wrote: post #57

Earlier quoted context omitted.

For me, it’s the confidence of knowing you’re hitting the right key. Memorizing how your layers are configured is nbd (it quickly become second nature). 42 keys (CRKBD?) allows you to confidently strike each key and confidently return to home. I’ve never been able to guarantee this if a single key is even 2 units away from home. That being said, I think the most important thing is that you like what you’re using. If…

> Memorizing how your layers are configured is nbd Ymmv; I have difficulty remembering the chords for keys I use once a week or once a month.

I put a lot of thought into where I map things. If I make sure it’s in line with my long term plan, then I never have to move it. I get the rarely-used mappings memorized eventually.

Re: Programming on 34 Keys

#69

Post by jhanschoo »

comfypotato wrote: post #68
jhanschoo wrote: post #61

Earlier quoted context omitted.

> Memorizing how your layers are configured is nbd Ymmv; I have difficulty remembering the chords for keys I use once a week or once a month.

I put a lot of thought into where I map things. If I make sure it’s in line with my long term plan, then I never have to move it. I get the rarely-used mappings memorized eventually.

As you helpfully state in your reply, that is not a nbd worth of effort. (Baseline effort being hunt-and-peck on dedicated keys)

Re: Programming on 34 Keys

#70

Post by comfypotato »

jhanschoo wrote: post #69
comfypotato wrote: post #68

Earlier quoted context omitted.

I put a lot of thought into where I map things. If I make sure it’s in line with my long term plan, then I never have to move it. I get the rarely-used mappings memorized eventually.

As you helpfully state in your reply, that is not a nbd worth of effort. (Baseline effort being hunt-and-peck on dedicated keys)

I see what you’re saying. What I meant is that I don’t actively work to memorize mappings. An initial effort/push when convenient to intelligently create the mapping is all that’s required. From there it happens naturally.

I was clarifying that the greatest hindrance to this process is changing your mappings (I get so confused if I ever try to move a custom mapping). I put in a little effort up front to make sure I don’t have to change the mapping.

Post reply on HN