Skip to content

Instantly share code, notes, and snippets.

@noopkat
Last active July 31, 2019 08:35
Show Gist options
  • Save noopkat/bfd09556d353638fdadd0ae9cf579e4c to your computer and use it in GitHub Desktop.
Save noopkat/bfd09556d353638fdadd0ae9cf579e4c to your computer and use it in GitHub Desktop.
Mech Keyboard Questions to ask yourself
  1. How many keys do you want ie. do you need function keys / cursor arrow keys / numpad?
  2. Do you like loud clicky keys, bumpy tactile, or linear fast to hit keys?
  3. Do you want to be able to swap out switches for different ones or mix / match your switches?
  4. Do you need it to be portable?
  5. Do you want LED lighting?
  6. Do you want to program it with macros to be highly custom?
  7. Do you want USB-c?
  8. Windows or Mac?
  9. Do you want split / ergonomic / ortholinear?
  10. Do you want to use custom / creative keycap sets or keep it OEM?
  11. The most important question is: are you ready to accept you'll never find one that meets every single one of your needs unless you make it from scratch, and even then there'll be compromises based on ability and material costs?
@KyleRConway
Copy link

  1. No num pad -- must have f-keys.
  2. MX-Browns
  3. Sure. Not high in importance.
  4. Yes. Relatively.
  5. Preferred.
  6. Preferred (I'm a linux-only, Dvorak user, so I'd prefer open source and on-board).
  7. Preferred (at this point it seems wise).
  8. Neither (Linux)
  9. Not required. More concerned about portability. Small preferred.
  10. OEM is fine.
  11. Yes.

Open to recommendations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment