Re: Futures

Le 22/04/2013 15:07, Kevin Smith a écrit :
>
>
>>     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
I see. I guess it's pretty much as much work as wrapping a native future 
for a library promise and vice versa.

David