Conversation

Notices

1. Embed this notice
   :ihavenomouth: (inginsub@clubcyberia.co)'s status on Saturday, 02-May-2026 19:04:03 JST :ihavenomouth:
   web devs cite this paper to say that no one needs latency lower than 200ms, despite it clearly saying that people who don't need to look at the keyboard will notice (tbf they are web devs, you can't expect them to be able to read)
   • Embed this notice
     troonigger (troonigger@clubcyberia.co)'s status on Saturday, 02-May-2026 19:38:21 JST troonigger

     in reply to
     @Inginsub "should be no more than 0.1 to 0.2 seconds"
     
     I always question the words of anyone who gives a threshold as a range of values.
     
     That nigger needs to tell us, is it 100ms or 200ms, do we split the difference and agree 150ms? Is it subjective, and we need to introduce a contingent variable?
     
     WHAT THE FUCK IS IT??!!! :blobcatangry:
     
     I'm hung over.
     :ihavenomouth: likes this.
   • Embed this notice
     ICScaryThings (icst@clubcyberia.co)'s status on Sunday, 03-May-2026 01:18:38 JST ICScaryThings

     in reply to
     @Inginsub It gets worse when you consider this was for old machines that the only concern was keyboard input and not something like a mouse which is significantly more annoying when it has latency or lag. I would saw anything more than mid double digits is noticeable really.
     
     Also since they were working with CRTs they only had two sources of noticeable latency, input delay and processing time, but now with LCDs you have to add that as well. The true latency is the sum of all of the delays in the loop from user input to a change on the screen. Since the developer doesn't have a good way to check what kind of cheap displays the user buys, worst case should be assumed and just leave enough margin.
     :ihavenomouth: likes this.