A Challenge Problem for Promise Designers (was: Re: Futures)

Domenic Denicola domenic at domenicdenicola.com
Fri Apr 26 10:03:24 PDT 2013


From: Tab Atkins Jr. [jackalmage at gmail.com]

> The need for this will decrease now that DOM Futures exist, and libraries switch to using those (or a subclass of them) rather than rolling bespoke promises.

Last I heard, jQuery has committed to never switching their promises implementation to one that works, for backward compatibility reasons. Rick might know more about if thinking has changed recently, though.

Even then, it's very naive to expect all code will be upgraded to subclass a DOM API.


More information about the es-discuss mailing list