A Challenge Problem for Promise Designers
bruant.d at gmail.com
Fri Apr 26 12:33:13 PDT 2013
Le 26/04/2013 20:36, Rick Waldron a écrit :
> The libraries discussed in this and similar threads have the benefit
> of very limited adoption, where breaking changes incur minimal costs.
> jQuery doesn't have that luxury ;)  and therefore won't break
> backward compatibility. I can assure you that we won't press for
> adoption of our implementation as a standard—despite its more than
> adequate qualification as a de facto standard (like it or not).
Which naturally leads to the question: why should platform promises be
compatible with Promise/A+ and not jQuery "promises"? Because more
libraries use Promise/A+? what about market share?
More information about the es-discuss