Live data from Hacker News

Programming on 34 Keys

peppe.rs

41–50 of 71 posts

Re: Programming on 34 Keys

#41
Man. People really want to live on hard mode.

When I see this layout I'm both amazed and thinking he must love copilot!

Back in the days we used to pay extra to have more buttons!

Extra F keys up top, two columns of function keys on the left etc.

This minimalistic trend with keyboards isn't really making people more efficient as it is a conversation starter.

Re: Programming on 34 Keys

#43

I'd be interesting in trying the opposite of this, a huge keyboard and no cording at all. Give all punctuation its own key. https://media.cybernews.com/2021/03/jqqpqja3j8n51-1024x655.j...

Typing on the second Japanese (or Chinese? Korean? Too small to make out) seems like a right pain.

Re: Programming on 34 Keys

#44
I went Miryoku on 36 keys, learnt to touch type and it’s honestly been the best thing I’ve done for my coding. I know it sounds extreme but I feel like never having to look at the keyboard means I stay in flow and make fewer mistakes.

It wasn’t that hard to learn. Time investment of about 30 minutes/3 times a week for about six month.

Re: Programming on 34 Keys

#45
post #41

Man. People really want to live on hard mode. When I see this layout I'm both amazed and thinking he must love copilot! Back in the days we used to pay extra to have more buttons! Extra F keys up top, two columns of function keys on the left etc. This minimalistic trend with keyboards isn't really making people more efficient as it is a conversation starter.

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 when typing blindly.

With fully programmable layouts the number of keys doesn't mean that much, though for me the sweet spot is around 42. Going much lower than that comes with too many compromises.

Re: Programming on 34 Keys

#46
post #35

my primary keyboards are a planck for my personal desktop and ergodox infinity for work. i guess if i used the planck every day i'd get used to it but i think that the braces/brackets/parens are common enough they deserve their own keys instead of chords. but again, i've not given the time to learn to type with chords as a daily driver. i would like one of these though and maybe move on from the planck for my desktop…

On the flip side, you could say they are common enough that they should be on the home row (accessed by a thumb-activate layer switch, of course).

Re: Programming on 34 Keys

#47

I'd be interesting in trying the opposite of this, a huge keyboard and no cording at all. Give all punctuation its own key. https://media.cybernews.com/2021/03/jqqpqja3j8n51-1024x655.j...

That's a great idea. I'd like something like the space cadet[1], but with function keys at the top and familiar arrow+ins/del/home/end/pgup/pgdown section.

[1] https://en.wikipedia.org/wiki/Space-cadet_keyboard#/media/Fi...

Re: Programming on 34 Keys

#48
I like weird keyboards. I have acquired, in order: a Kinesis Advantage 2, an Ergodox (split ortholinear), a OLKB Planck Light (40% ortho), and a OLKB Preonic (60% ortho).

I've been daily driving the Preonic for 4 years now and once reconfigured, it is the most comfortable of my keyboards. The layer system is a game changer: you can put arrow keys on the home row, just a modifier away. One other cool trick is having enter on the bottom right key, you can press it with your palm.

I describe a bit my current layout in the QMK repo (they encourage everyone to add their keymap!): https://github.com/qmk/qmk_firmware/tree/master/keyboards/pr...

Re: Programming on 34 Keys

#49

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…

Would you be willing to link your ML layout?

Re: Programming on 34 Keys

#50
post #41

Man. People really want to live on hard mode. When I see this layout I'm both amazed and thinking he must love copilot! Back in the days we used to pay extra to have more buttons! Extra F keys up top, two columns of function keys on the left etc. This minimalistic trend with keyboards isn't really making people more efficient as it is a conversation starter.

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…

Yeah nowadays I stick to TKL.
Post reply on HN