David Bruant bruant.d at
Tue Nov 6 11:15:38 PST 2012

Le 06/11/2012 20:07, Axel Rauschmayer a écrit :
> That’s at a weird intersection between HTML5 and ECMAScript, (...)
I think it's more historical than anything. The event loop, 
setTimeout/Interval (and promises) belong to the language (ECMAScript), 
not to a library (HTML5) in my opinion.
ECMAScript 1-5 were concurrency-neutral. A pure ES5 programs has a start 
and an end and that's it. No concurrency whatsoever.
ES6 is going in that direction too.
ES7 opens a breach to event loop concurrency with async observers 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list