Hacker News Reader

> This program measures end-to-end latency: it emits keypress events and captures the screen to note when it gets updated (as actually visible to the user)

> [...]

> The screen resolution was 1920x1080 and the LCD refresh rate 60 Hz

How exactly can xterm have an average end-to-end latency of 2ms, if on average you need to wait 8ms for the next frame?

View on HN

By sending all key-press events an average of 2ms before the next frame is rendered

But the next frame takes a while to actually show up on the screen, so the "as actually visible to the user" part simply can't be right. This may be isolated latency of just the program, but definitely not something reflecting real-world user experience, it's 1-2 orders of magnitude off in that regard.

Reply on news.ycombinator.com