Le 09/08/2014 16:22, Brian Kardell a écrit :
On Aug 9, 2014 10:16 AM, "David Bruant" <bruan...@gmail.com
<mailto:bruan...@gmail.com>> wrote:
> There is still a case for blocking primitives for projects that
compile from other languages (C, C++, Python, Java, C#, etc.) to JS [3].
>
I'm glad to be switching last night's twitter discussion to a bigger
medium. My question here is: what is the proposal (if there is any)
to balance these and simultaneously ensure that we don't wind up
limiting ourselves or providing really bad foot guns or two APIs
depending on whether you're in the main thread or a worker?
There isn't such proposal and I don't think that can exist which is one
reason I'm opposed to the introduction of blocking primitives in workers.
I really hope the compile-to-JS use cases will find another way to be
solved.
David
