trying to popularize #responsivity and teach people about #latency: “You’ve probably come across a website where scrolling stutters now and then, a button responds slightly late, or the letters you type into a search box show up half a beat behind. It isn’t bad enough to be annoying, but it gets on your nerves in a subtle way. That kind of jank is what a blocked main thread looks like. (...) web performance metrics. INP (Interaction to Next Paint), which measures how long it takes for the screen to respond after the user does something, and TBT (Total Blocking Time), which measures the total time the main thread was blocked during page load”
Includes details that I didn’t know about setTimeout and something called MessageChannel in #JS. Doesn’t mention web workers, though.
John #Carmack on a style of programming where you inline all your code and do not use any subroutines. “As an additional confirmation of the point of the article, a couple years later when I was working on the Doom 3 BFG edition release, the exactly predicted off-by-one-frame-of-latency input sampling happened, and very nearly shipped. That was a cold-sweat moment for me: after all of my harping about latency and responsiveness, I almost shipped a title with a completely unnecessary frame of latency.” #latency #real-time #responsivity #games #video-games #software-design
on 02024-09-03notes on #WCET for #music #audio #real-time #responsivity in #SuperCollider
on 02024-02-06