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

Re: =[xhr]

From: Brendan Eich <brendan@secure.meer.net>
Date: Wed, 03 Sep 2014 08:34:41 -0700
Message-ID: <54073511.5090103@secure.meer.net>
To: David Rajchenbach-Teller <dteller@mozilla.com>
CC: public-webapps@w3.org
David Rajchenbach-Teller wrote:
> Clearly, it would require big changes, although compiling to return
> Promise and using Task.js + yield at call sites would probably be much
> simpler than CPS conversion.

All call sites, every last Java method => JS function call? That means 
every single function becomes a generate, all functions use yield and so 
become generator functions, all calls construct a generator which must 
have .next() called to get it started. The performance is not going to 
be tolerable.

This vague suggestion has come  up with Emscripten re: sync APIs for 
workers, and it's a bogus hand-wave. Please don't suggest it as a 
solution and then make definite plans to reject sync APIs in workers or 
schedule removal of XHR's async=false mode on a date certain!

Received on Wednesday, 3 September 2014 15:35:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:26 UTC