Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Mandatory reading when it comes to keyboarding: http://oreilly.com/news/zenclavier_1299.html

So far, I've used many keyboards. Nothing comes close to the IBM Model M, or their modern incarnations. Here in India, you get a TVS Gold keyboard which is the basically IBM Model M of India. The difference between that and my office HP standard keyboard is so enormous, I can nearly write a short book detailing it.

Firstly the build, Model M's ones are built like a tank. They will last decades. Secondly the spring feedback and clicky auditory feed back you get. Thirdly, and the most important feature of the keyboard is the impedance match when your fingers hit the keyboard and the resistance/friction those keys offer. The Model M some does this so well, you will almost feel you are becoming one with the keyboard, combined with this the clicky auditory feed back and the rugged build is what makes the IBM Model M the king of all keyboards.

Now every time I use the Model M at home and then come and use the keyboards at office, I see two straight issues. One I see is either the keyboard is offering too much friction/resistance which in case my fingers hit the keys faster but the keys don't mechanically respond as faster, or in cases of keyboard like the Apple's flat aluminum keyboard the resistance is too less and fingers tend to slower compared to the keys. And yes the feed back thing isn't in any way remotely comparable to the Model M.

Lastly you can argue that, this should even matter to you as a coder. As good coding is above typing skills. Though I agree with you, I would suggest you read the article I posed at the top of this comment.

Beyond all, once you've some really awesome. Even the very normal all begins to feel like bad.

Long story, short- a good geek/nerd keyboard needs to:

    1. Provide auditory feed back while typing.
    2. The impedance match between the key response and
    your finger's hit force need to match perfectly.
    3. Keyboard must be rugged.
    4. Important code related keys should be big.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: