3 ms·
I don't disagree with you in general and I find the lack of focus on latency very frustrating (though the proliferation of 120hz screens seems to indicate that
by errantspark 5y ago
I don't disagree with you in general and I find the lack of focus on latency very frustrating (though the proliferation of 120hz screens seems to indicate that there's hope)
But with regard to the Dan Luu post I've tried to recreate his findings and maybe things have gotten better because with 170hz monitor and a run of the mill gaming keyboard I'm getting keypress to photon latencies in windows gVim of about 35ms as measured with a high speed camera.
- tobz1000 5y agoThis is made irrelevant for 90% of users who then use their keyboard & monitor in Discord, VS Code, and dozens of other JS-powered programs and sites.
- errantspark 5y agosigh JS is imperfect but it doesn't just make everything it touches slow. I would be very surprised if in Discord for example any JS was blocking between you pressing a key and the key appearing in your text box. In fact I took the time just now to run a few samples in Discord and it's looking like I'm getting the same 35-40ms keypress to photon latency as gVim with one 80ms outlier out of the 5 runs I did.
- tobz1000 5y agoThe difference is very noticeable on a less-than-new CPU (my x240 with an i7 4600U for example) when the text input triggers other UI changes. Even on my Ryzen 3600, switching channels in Discord has visible lag, regardless of network activity. Compare this to any operation in Sublime Text/Merge and the difference is obvious. The implication is also that more battery power is used for every action (not to mention vastly more memory), which matters for machines of any capability; but these are not latency-related concerns.