3 ms·
instead of chaining together shorter timeouts, why not calculate the datetime of the delay and then invoke via window.requestAnimationFrame (by checking the cur
by darepublic 2y ago
instead of chaining together shorter timeouts, why not calculate the datetime of the delay and then invoke via window.requestAnimationFrame (by checking the current date ofc).
- deleted 2y ago[deleted]
- augusto-moura 2y agoAre you suggesting checking the date every frame vs scheduling long task every once in a long while? Can't tell if it is ironic or not, I'm sorry (damn Poe's law). But assuming not, it would be a lot more computationaly expensive to do that, timeouts are very optmized and they "give back" on the computer resources while in the meantime
- darepublic 2y agoNo irony intended I can be this dumb. Your point did occur to me as I posted, was just grasping at straws for a "clean" solution
- jw1224 2y agoUnlike setTimeout, requestAnimationFrame callbacks are automatically skipped if the browser viewport is minimized or no longer visible. You wouldn’t want to miss the frame that matters!
- chii 2y agoalso, not to mention that setBigTimeout would still work in serverside js, while requestanimationframe doesn't!