On 4 nov, 07:00, Alan Gutierrez <a...@prettyrobots.com> wrote:
The setTimeout(ƒ,0) behaving as a nextTick(ƒ) is the proper behaviour
for a setTimeout(ƒ,0) with no clamping (the browsers clamp it to a
minimun of several ms, mainly due to a bug in jquery).
But, the setTimeout(ƒ,1) behaving as a setTimeout(ƒ,0) is *clearly* a
Node's timers have always been buggy -and still are- for example this:
may fire a then b, or b then a, which is another bug.