W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2013

Re: Coordination (was: ES6 Modules)

From: Kevin Smith <zenparsing@gmail.com>
Date: Sat, 13 Apr 2013 19:52:48 -0400
Message-ID: <CA+mDt2zQh6k4PK_mnW2t1nnynYrO2kNbU=vBNFrAse2u+UMt0Q@mail.gmail.com>
To: Dirk Pranke <dpranke@chromium.org>
Cc: Sam Tobin-Hochstadt <samth@ccs.neu.edu>, Brendan Eich <brendan@mozilla.com>, Robin Berjon <robin@w3.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Erik Arvidsson <erik.arvidsson@gmail.com>, es-discuss <es-discuss@mozilla.org>
> Put concretely: if Futures are provided via libraries, but you can't
> assume (require) libraries, then you can't design DOM APIs around Futures.
> Clearly, one way to solve this is put Futures into the language, but
> another is to solve the extensibility problem so you can start requiring
> libraries.

I don't understand this.  Surely you wouldn't design a *platform API* to be
dependent on userland JS libraries.  No?

{ Kevin }
Received on Saturday, 13 April 2013 23:53:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:48 UTC