I used the wireless Apple keyboard for a while but I missed Home/End/Page Up/Page Down. Also had a lot of trouble swapping it back and forth between my OSX and Windows machines.
At least the CODE keyboard will add more variety. At the end of the day that's what people really need.
That said, everyone has their preferences. I think someone else in the comments mentioned how it would be nice to have a fully 100% customizable keyboard. I agree with that idea.
Augh! Don't do that! Remap it to something useful! CTRL is popular, but I'm loving backspace, personally. It's a key that never comes up if you just count keys based on taking text file samples, but I for one like having it available where it does not rip my fingers off the home row. (Since I use Dvorak, the home row is actually meaningful to me, since it is useful, unlike the standard QWERTY homerow.) But I don't really care what you remap it to, just don't leave such valuable space sitting there!
Backspace (the original one) I remapped to switch active windows. I've really been eyeing that Tab key, too; it is not unused (many emacs programming modes use it as "reindent this line to the proper level"), but I've wondered if it couldn't be a bit more effective. Not sure what to reassign it to yet, though.
- On OSX: https://pqrs.org/macosx/keyremap4macbook/
- On Linux: https://github.com/alols/xcape
You have one. It's the one you typed that post on. A keyboard just emits numbers, it's up to the computer OS to determine what to do with it.
Exactly how to customize your keyboard is OS-specific, but it can be done in all the major ones, as far as I know. (Can't commit to Windows 8. Windows 7 did require some unpleasant registry hacking for changing caps lock.)
If you want control over what your keyboard does, take it.
Incidentally, the big key to trying things out is that if you remap a new function onto Caps Lock and you want to see if it works for you, be sure to demap the other copy of the key. If you make Caps Lock a new Backspace, you'll never use it. If you make Caps Lock a new Backspace, and then demap the current one, you'll literally be adjusted in a matter of minutes, and if you decide you don't like it, returning is also a matter of minutes.
Once you work out what you need to do for your OS, keyboard layout experimentation is far more rapid than people realize, I think.
Hard to conceive of spending that much and having to continue typing after all. If I had that kind of money, I'd have a keyboard chauffeur.
http://www.kinesis-ergo.com/advantage.htm
Don't be cowed by the esoteric appearance; it's really just a tweak on the standard layout.
[1] http://www.cherrycorp.com/english/keyboards/POS/SPOS_Rows_Co...
I abhor the location of capslock/control because when I was first learning to program I only used terminals where control was the key where caps lock is. When I was forced to used keyboards that had control down at the lower left I went from using EMACS to using vi because of the annoyance.
That said, folks can adapt and much of what you do is muscle memory anyway. On your brackets idea I actually like that brackets are matched both unshifted and shifted on my keyboard. so {} and [] are both easy to type. Since I rarely type ctrl-] or ctrl-[ having those keys map to ( and ) might be useful but I don't look at my keyboard when I type so I really can't say.
For me it is all about reliably hitting the key I mean to hit. If I can do that I can adapt to most things.
[1] See "The Mote in God's Eye" by Pournelle.
ha! no. seriously, you can change any key you want on the keyboard to suit your preference coding/language style
I agree with you regarding the brackets - < >, ( ), etc. ... but / and \ have nothing to do with each other.
However, I have mixed feelings with several of the author's specific points.
1. In general, I think a keyboard should retain all legacy keys, including Scroll Lock and Printscreen because they have acquired specific meaning through their many years. If a new keyboard were paired with a new operating system, then I'd be comfortable--even happy--with disposing of legacy. As it is though, Printscreen is the easiest way to grab a screen-capture or window-capture.
2. The CODE keyboard may be marketed as designed for programmers, but it seems to also carry over a certain "gamer programmer" target. Hence, the PS/2 adapter (I believe some harder-core gamers profess to PS/2 being faster).
3. Space is indeed very important. I am not sure if the author is just pointing that out matter-of-factly or intends it as criticism. I assume the prior.
4. Very much agree that Caps Lock should be diminished in importance. It should be located on some fringe alongside Scroll Lock. Many of my colleagues and I simply disable the key outright.
5. Also agree that backslash should be diminished in importance. However, I personally would like a "programmers keyboard" that made all variations of brackets < > ( ) [ ] { } / \ available (a) without modifier keys of any sort and (b) in side-by-side pairings. It bothers me that / and \ are not side-by-side on most/all keyboards.
6. Strongly disagree that Page Up (and presumably Page Down, although it's not cited by name) is a dumb key. I press Page Up, Page Down, Home, and End hundreds of times per day.
7. I don't actually like that function keys are often trimmed to half-height even on desktop keyboards. That is fine for a laptop. But on my desktop, I have the room for an additional row of full-height keys, thank you. In general, desktop keyboards that are built to laptop aesthetics are dubious to me.
8. Strongly disagree that arrow keys lack importance. I smell a vimmer. Oh, sure enough, he mentions the ADM3A. Please, I beg of you, vimmers: don't pretend to speak for all programmers.
9. Strongly agree with the premise that a programmer's keyboard should avoid use of modifier keys for symbols. I have often ranted that programming language designers should avoid arrow operators -> and => in their syntax because of the shift transition required to type an arrow on most keyboards.
I like the premise of this blog entry a great deal! Please, let's see some actual innovation in programmer's keyboards. But apparently, we should have one style for vimmers and one for other programmers. :)