1. Offloading work from the main thread
Many commenters stress moving heavy work off the UI thread using web workers, requestAnimationFrame, or cooperative yielding.
- “We work in WASM and are considering web workers to help with rendering documents off the main thread in that context.” — piker
- “I wish await in JavaScript could conditionally yield. Instead I end up having to use arounds like if (shouldYield()) await do yield();” — adzm
2. Critique of over‑engineered sites and framework bloat
A recurring opinion is that most websites don’t need heavy SPAs or large bundles; the performance problems often come from unnecessary technology.
- “My point is that many websites are using way too much technology for what they need to do, with correspondingly long load times and choppy runtime behavior.” — ahartmetz
- “The issue is though that it's too focused on interactivity… 90%++ of slow sites are not slow because of interactivity really, they are slow because they ship enormous react/nextjs bundles and have extremely heavy hydration work to do.” — martinald
3. Performance & responsiveness, especially on low‑end devices
Developers highlight the importance of keeping frame budgets, avoiding jank, and ensuring usability on modest hardware or slow connections.
- “On the price ticket example, on my device (Samsung A15, mediocre phone from 2024) I get 11 fps with the slow example and 30 fps with the fast one.” — andai
- “The browser can easily handle millions of calculations and then render a million DOM elements so quickly that you won’t even notice it. The problem is when you try and do this hundreds of times very second.” — mr_toad