>
> Okay, so how will end users or jQuery authors upgrade their promises to
> become ES6-compliant?


I don't know enough about jQuery's internals to write convincing code, but
the basic idea is that you feature detect for ES6 Promises.  If that test
passes, then you implement jQuery.Deferred using a Promise subclass (which
would do assimilation for backward compatibility reasons).  Otherwise you
implement it the old-fashioned way.

Application developers who are going to hook into the new DOM API's need to
upgrade their jQuery.

Of course, jQuery promises will still over-assimilate objects which have a
`then` method but aren't "thenable", but that's jQuery's backward
compatibility problem, not the entire language's.

Am I missing something?  I usually do...  : )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20131220/9d1ff29b/attachment-0001.html>

I don't know enough about jQuery's internals to write convincing code, but
the basic idea is that you feature detect for ES6 Promises.  If that test
passes, then you implement jQuery.Deferred using a Promise subclass (which
would do assimilation for backward compatibility reasons).  Otherwise you
implement it the old-fashioned way.

Application developers who are going to hook into the new DOM API's need to
upgrade their jQuery.

Of course, jQuery promises will still over-assimilate objects which have a
`then` method but aren't "thenable", but that's jQuery's backward
compatibility problem, not the entire language's.

Am I missing something?  I usually do...  : )