Programming

25780 readers

172 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Keyboard latency (danluu.com)

submitted 3 days ago by HaraldvonBlauzahn@feddit.org to c/programming@programming.dev

17 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] HaraldvonBlauzahn@feddit.org 5 points 3 days ago* (last edited 3 days ago) (2 children)

50 ms is clearly noticeable. Dan Luu mentions 2ms in the original post.

Try in a terminal

read a; sleep 0.02; echo $a

and vary the number.

Actually, the time resolution for visual sensations is at least 5ms and for sound it is even smaller - a drummer in s band needs to practice a lot to get the right beat.

[–] ulterno@programming.dev 0 points 1 day ago

I could notice it at 0.05 (well I tried 0.05 right after 0.02, so maybe it would work at lower too)
I would guess I might notice 0.02 if it were music.

[–] MonkderVierte@lemmy.zip -1 points 3 days ago

Terminal echo is not a good measure, far too slow. Make it a C program.