Skip to content
View letmegobacktosleep's full-sized avatar

Block or report letmegobacktosleep

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
letmegobacktosleep/README.md
  • Hi, I’m @letmegobacktosleep
  • I am currently attempting to develop my own hall-effect keyboard

I am strongly against keyboards having a polling rate >1KHz, because unlike a mouse which has audible and tactile feedback, or almost instant visual feedback when it comes to moving it around, keyboards typically have very little visual feedback, and a tactile feedback which either doesn't align with the actuation of the key, or no tactility on linears, which already messes with, and therefore destroys any reason for the absolute highest polling rate possible.

Even with hall-effect keyboards where you only have to move the key approximately 0.2mm to have it actuate reliably, the visual feedback on the screen is nowhere near as much due to almost all games having some kind of "movement acceleration" which makes the difference between 2ms latency (worst case at 1KHz) and 0.125 latency (best case at 8KHz) imperceptible.

Pinned Loading

  1. qmk_userspace qmk_userspace Public

    Forked from qmk/qmk_userspace

    Userspace for the open-source QMK keyboard firmware.

    Shell

  2. treebot treebot Public

    Python