Musical instruments become unplayable around 50-100 ms of audio latency, but that range is the *best case* for our computers' video response! https://danluu.com/input-lag 100 ms is the space between two vim commands at 100 WPM. In a 300 WPM burst it's the space between four commands!
-
Show this thread
-
Few of us have ever done programming with less than ~100 ms of latency. We don't even know how it would feel. If you want to know whether 100 ms is noticeable, try intentionally breaking your editor by adding an extra 100 ms of synthetic latency. You'll probably notice it.
6 replies 3 retweets 27 likesShow this thread -
This isn't about monitor refresh rate. 60 Hz is 17 ms per frame, which is a relatively small part of the ~100 ms input latency of current computers. Higher refresh rates are great for smoothness of motion but they don't fix input latency.
1 reply 0 retweets 9 likesShow this thread -
One relatively easy way to experience a bit of extra latency: SSH to a machine where your ping is ~50 or less, then use vim. It's very obvious when you're vimming over SSH.
6 replies 1 retweet 23 likesShow this thread -
Replying to @garybernhardt
I'm not sure if this is just me seeing something I want to see, but it always "feels" like Vim in a virtual terminal is just a little more responsive that Vim in a GUI terminal.
1 reply 0 retweets 0 likes -
Replying to @hillelogram @garybernhardt
This is true in some cases - I don't remember the exact measurements (possibly
@danluu still has them), but I remember there being at least a ~50ms difference between VT and whatever terminal emulator setup I was using inside X. Likely depends on the terminal emulator, though.1 reply 0 retweets 0 likes
According to my notes, we saw 160ms vs. 100ms in your standard terminal vs. the other mode.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.