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

Re: Futures

From: Kevin Smith <zenparsing@gmail.com>
Date: Mon, 22 Apr 2013 09:07:17 -0400
Message-ID: <CA+mDt2xMU2dWNQLB5e=NSn3wFph=0yNYC6+3A3T65i+wadcFzg@mail.gmail.com>
To: David Bruant <bruant.d@gmail.com>
Cc: Anne van Kesteren <annevk@annevk.nl>, Brendan Eich <brendan@mozilla.com>, "Mark S. Miller" <erights@google.com>, Douglas Crockford <douglas@crockford.com>, Markus Lanthaler <markus.lanthaler@gmx.net>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Norbert Lindenberg <w3@norbertlindenberg.com>, es-discuss <es-discuss@mozilla.org>
>
>
> What about using a symbol for the `then` protocol?  Libraries can be
> upgraded to use the symbol as an alias for `then`.  It set up a dependency
> on ES6, of course...
>
> And it doesn't address the compatibility problem people want to address.
>

It still does I think.  It's cheap for a library to add a symbol-named
alias for `then`.  But it's expensive for a library's clients to replace
all usage sites with a different API.  Even though `then` is standard, the
other parts are not.

- Q.defer
- new jQuery.Deferred
- new Future
- ...etc

{ Kevin }
Received on Monday, 22 April 2013 13:07:44 UTC

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