Proper Handling of Set Intervals in Browser Development

1min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

To ensure accurate time calculations in the browser, it is crucial to use timestamps to track start time and continuously compute time differences in each loop. Set intervals may not run at precise intervals due to background processes like switching apps or tab snoozing. Prolonged set intervals can drain battery life and potentially be disrupted by blocking code. The function scheduled by set interval is placed at the end of the event loop queue, which may be delayed if preceding tasks are resource-intensive.

In this potluck episode of Syntax, Wes and Scott discuss egress, scraping, Safari EU changes, and answer questions on updating dependencies and SetInterval.

Show Notes

00:00 Welcome to Syntax!
01:35 Brought to you by Sentry.io.
02:49 I have over 100,000 user images on Cloudinary. How do I migrate to another service?
Cloudflare-Cloudinary Proxy
07:27 Switching from Mac to PC.
Figma, DaVinci Resolve
12:32 What’s your take on the Safari 17.4 PWA removal debacle for EU users?
Bug Report
Fullscreen API Bug Report
19:45 Is there any clear front-runner when it comes to monorepo tools?
23:44 Some big web apps have a div relatively high in the DOM with a class like “scroll-container” or “cursor-events”, why is that?
32:15 Is ChatGPT Plus worth it? I’m trying to avoid death by 1000 subscriptions.
ElevenLabs
37:47 Performance vs accuracy when working with timers.
40:37 How do you update the dependencies to work with a current version of Node? Also, if you are building from scratch, how do you determine what dependencies to use?
Syntax show 425: Updating Project Dependencies
45:52 Clarification on the browser blocking.
Mozilla’s vision for Firefox MV3
49:19 Problems when working with JavaScript’s new Date().
54:27 Sick Picks + Shameless Plugs.