> I'm not so sure. I used to use a 30Hz display while waiting for a driver update (was a 4k early adopter), and I found programming with a 33ms key latency to b

> I'm not so sure. I used to use a 30Hz display while waiting for a driver update (was a 4k early adopter), and I found programming with a 33ms key latency to be maddening Because of stupid software licences, I have to work a lot in remote desktop when I'm working from home. So I work with latency while typing all the time. It was maddening in the beginning, but I got used to it quickly. I think the key is that you have to be able to touch-type without relying on close-loop feedback. If your error rate is low enough, you quickly learn to trust your fingers. After that, all you need to relearn is cursor positioning - you can't hold down arrow keys (or HJKL in vim) ever. It forced me to rely on moving the cursor x words/paragraphs at a time, and to use the mouse a little more.