Typing with pleasure, and low latency

> Because sampling rate is fast enough to misinterpret contact bounce as keystrokes, keyboard control processor perform so-called debouncing of the signals by aggregating them across time to produce reliable output. Such a filtering introduces additional delay, which varies depending on microcontroller firmware. As manufacturers generally don’t disclose their firmware internals, let’s consider typical debouncing algorithms and assume that filtering adds ~7 ms delay, Since it's debouncing rather than outright…

Great to see this quantified! My pet peeve is laggy interfaces. I'm not surprised to see Atom on there, because browsers do seem to have a big problem with this. Ubuntu seems to have a big problem with this too, e.g. in the native "gedit". Back in the Ubuntu 4.0 days (2006 or so), the default terminal was really slow. I didn't really know how to use Linux then, so I would SSH into with Putty on Windows, and use…

This mirrors one of the things that I 'feel' about using Vim, that I commented about a few months ago [0]. It just feels faster than using something like Atom / Visual Code, it's hard to explain in other terms, but this at least shows the actual latency values that cause the feeling. The great thing from these graphs is that it shows the consistency of performance with Vim across pretty much all platforms. So once you're using Vim it's…

Typical average latency of keyboard and monitor combined is about 26 ms 'typical' might be a bit of a stretch here: I doubt that without tuning settings on a standard OS like Ubuntu/Windows and with your typical 60 or 75Hz monitor it's possible to achieve numbers this low (I've measured software->monitor latencies, good luck getting lower than 2 frames, and that's excluding input and processing). Anyway since this is largely theoretical, what would be really interesting here to actually measure…