Visual explanations, generated live
Don’t just read it.
Move it. Change it. Grasp it.
Turn a developer concept, error message, or code snippet into an explorable explanation you can manipulate.
Instant examples
Your explainer
See the system, not just the definition.
AI chose stepper · Order and movement are the idea, so a step-by-step timeline makes the scheduling rules visible.
The JavaScript event loop
Watch work move between the call stack, browser APIs, and the task queues as the runtime decides what executes next.
This is why a resolved promise can log before a zero-delay timer.
Call stack
Runs nowmain()
Logs A, schedules both callbacks, then logs D
Web APIs
Waiting outside JSsetTimeout callback
A timer schedules a future task
Microtasks
PromisesPromise.then
A resolved promise schedules a microtask
Task queue
Timers & eventsStep 1 of 4
Run the script
main() logs A, registers a timer, queues a promise reaction, then logs D. Statements execute inside the script; they are not separate stack frames.
Synchronous work always wins first.
Prove it in code
console.log('A');
setTimeout(() => console.log('B'), 0);
Promise.resolve().then(() => console.log('C'));
console.log('D');What does this print?
Interview mode
Can you explain it under pressure?
Three questions from foundation to application, including a code-output check.