3 ms·

On my iPhone I find everything up to maybe 0.6 seconds to be just fine. Part of this may be being used to using SSH over VERY poor network connections. I think

On my iPhone I find everything up to maybe 0.6 seconds to be just fine. Part of this may be being used to using SSH over VERY poor network connections. I think the biggest frustration with latency is not the latency itself, but rather when latency is combined with the possibility that what you entered didn't register at all and the time pressure of having only 15 seconds of signal to submit your command - situations that often occur when using Internet based sessions in the wild. The other source of annoyance is trying to "not crash the system". Often when a system presents high latency like this, I tend to consciously pay attention to how many "buffered" inputs I'm sending for fear of crashing something, and that self-throttling can get tiring.

crooked-v 7y ago
Don't forget the classic "while you tried to click on something, something else moved in the way of it" problem.
- rossdavidh 7y ago
  My pet peeve, way more annoying than latency.
- chendragon 7y ago
  Bonus points if this results in mis-clicking something dangerous or irreversible, like "delete", "cancel","post","send", "close", "exit without saving" or the like.
  - hunter2_ 7y ago
    In the same way that browsers refuse to do certain things unless coupled with human input (like open a pop-up window, or submit auto-filled form data), they should refuse to send a click event to an element that hasn't been stationary for a short while. It would need to be defeatable for "game mode" though, for games involving clicking moving targets. Any other edge cases to consider?
    - kd5bjo 7y ago
      This is why most platforms provide both raw and semantic events: mousedown and mouseup are instantaneous and reflect the raw input, but click is meant to describe user intent to initiate an action. Leaving the raw events for games but requiring semantic events for dangerous actions seems like a decent compromise.

crooked-v 7y ago

Don't forget the classic "while you tried to click on something, something else moved in the way of it" problem.

rossdavidh 7y ago
My pet peeve, way more annoying than latency.
chendragon 7y ago
Bonus points if this results in mis-clicking something dangerous or irreversible, like "delete", "cancel","post","send", "close", "exit without saving" or the like.
- hunter2_ 7y ago
  In the same way that browsers refuse to do certain things unless coupled with human input (like open a pop-up window, or submit auto-filled form data), they should refuse to send a click event to an element that hasn't been stationary for a short while. It would need to be defeatable for "game mode" though, for games involving clicking moving targets. Any other edge cases to consider?
  - kd5bjo 7y ago
    This is why most platforms provide both raw and semantic events: mousedown and mouseup are instantaneous and reflect the raw input, but click is meant to describe user intent to initiate an action. Leaving the raw events for games but requiring semantic events for dangerous actions seems like a decent compromise.