91–100 of 110 posts
I took out the o-rings because they made it too gummy. It was very stiff for a bit when I did that, but I got used to it and now I can play games of CS:GO and code on it just fine.
I recommend it, it's simple, small and feels solid.
What makes this different to the keyboards with the exact same feature set that are established for years and years already (Filco, DAS, happyhack...)?
This is the keyboard Jeff Atwood was talking about I think: http://blog.codinghorror.com/the-code-keyboard/
Yawn! I've been using my HP c3753a for 18 years now (same layout as these, great feel and sound (similar to IBM M)). If it ever dies, I'll just use the backup I grabbed 10 years ago. It's kind of like buying new antique furniture. I'm sure the keyboard is solid and will last, but I've got the original...
Earlier quoted context omitted.
I don't understand the attraction of backlighting in "programmer" keyboards. Seems like it would only benefit people who look at the keyboard. Which explains why it's popular on consumer laptops, but not why any computer professional would want it.
I wouldn't think so either until I received my first one - its surprisingly useful. In fact my current backlit mechanical keyboard is one of my favorite purchases in the past few years for me - for something I use so much, spending $100-$200 is as much of a no-brainer as a great office chair.
Because I'm a touch typist I keep my back-lights toggled off.
Earlier quoted context omitted.
I don't understand the attraction of backlighting in "programmer" keyboards. Seems like it would only benefit people who look at the keyboard. Which explains why it's popular on consumer laptops, but not why any computer professional would want it.
I don't look at it while coding, but what about when you need to adjust the volume when watching a film?
On the CODE keyboard your VolUp/VolDown is PgUp/PgDn, combined with the Fn key.
What makes this different to the keyboards with the exact same feature set that are established for years and years already (Filco, DAS, happyhack...)?
The Code name as far as I can tell. Got three different cherry red/black 87 keys (AKA tenkeyless), including a Filco and a cheapo chinese one. And I can not see what this one bring to the table. This is the keyboard Jeff Atwood was talking about I think: http://blog.codinghorror.com/the-code-keyboard/
Could someone explain what makes this a "code" keyboard? I was expecting to see a keyboard with some actual ergonomics to help reduce wrist strain.
I would really love a mechanical keyboard in the split ergonomic layout of a Microsoft Natural Ergonomic keyboard. Something about that shape feels right to me, but most mechanical keyboard either use a standard layout or something radically different (I'm looking at you Ergodox).
What about using two full keyboards, one for each hand? The question is, will they cooperate? I.e. holding a modifier key one one keyboard affects keys pressed on the other keyboard? If so, I think I would like using two small separate keyboards.
For people who want an ISO layout, custom keycaps or greater choice of switches, the WASD V2 is identical to this except without the backlighting (how often are you at your desk with the lights off?). I've owned one for a year and it's been fantastic. http://www.wasdkeyboards.com/index.php/products/mechanical-k...
I don't understand the attraction of backlighting in "programmer" keyboards. Seems like it would only benefit people who look at the keyboard. Which explains why it's popular on consumer laptops, but not why any computer professional would want it.
When I bought my laptop, backlit keyboards weren't standard. Now they are and I'm looking forward to getting a new one.
Earlier quoted context omitted.
Assuming that you mean the Advantage, the brackets were always awful. I gave it up for a HHKB
When you say that the "brackets were always awful", are you referring to their placement? If so, the Kinesis Advantage is programmable, so why didn't you relocate the brackets?