Save 1 millisecond!

[James-Dunn]

The default action of setTimeout will move the function to the end of the call stack. No need to wait one millisecond.

[oriSomething]

it won't help, setTimeout at the minimum delay in 4 seconds. the only option to save time is using postMessage

[James-Dunn]

It doesn't look like current browsers observe that spec. Testing it on Chrome/Firefox seems to show no minimum for me. http://jsbin.com/foloponuli/edit?html,js,output The word "second" appears first for me if the first timer is set at 2 ms or higher on Chrome, and 1 ms on Firefox.

[oriSomething]

you don't test it right. the browser will execute setTimeout(..., 1) before setTimeout(..., 2), no matter what the order, but still the first that will run is after 4ms.

[oriSomething]

edited:
read this

[megawac]

@oriSomething has it right. On another note @jdalton and to derail this a bit, want to consider using setImmediate or process.nextTick where available in v4?

[oriSomething]

also using MessageChannel / postMessage as a polyfil might be helpful

[jdalton]

We avoid a setTimeout of 0 because I believe old Chrome could end up blocking the UI thread with them. I avoid setImmediate because there's no clean way to cancel them with clearTimeout.

There is runInContext which allows you to customize.

var defer = require('lodash').runInContext({ 'setTimeout': setImmediate }).defer;

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.