W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

Re: Blocking message passing for Workers

From: David Bruant <bruant.d@gmail.com>
Date: Tue, 12 Aug 2014 01:56:14 +0200
Message-ID: <53E9581E.8080901@gmail.com>
To: Brian Kardell <bkardell@gmail.com>
CC: Glenn Maynard <glenn@zewt.org>, adelespinasse@gmail.com, public-webapps WG <public-webapps@w3.org>
Le 09/08/2014 16:22, Brian Kardell a écrit :
>
> On Aug 9, 2014 10:16 AM, "David Bruant" <bruant.d@gmail.com 
> <mailto:bruant.d@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
Received on Monday, 11 August 2014 23:56:44 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:16 UTC