Diskussion: Die JavaScript-Ereignisschleife: Tasks, Microtasks und Rendering

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Übersetzung nicht verfügbar; das Original wird angezeigt. Original

Two details for the chunking advice. The HTML standard clamps nested timers: once `setTimeout` calls are nested more than five levels deep, any delay below 4 ms is raised to 4 ms, so a loop that yields with `setTimeout(r)` on every chunk pays at least 4 ms per chunk after the first few. The classic workaround is to yield through a `MessageChannel` message, which is a task without the clamp; the newer one is `scheduler.yield()`, which returns a promise that resumes as a prioritised continuation, so input handled in between does not push the loop's remaining work behind everything else in the queue. MDN lists `scheduler.yield()` as limited availability (Chromium ships it), so feature-detect it and fall back to the timeout.