Promises Consensus with /A+ terminology

Tab Atkins Jr. jackalmage at gmail.com
Thu Aug 1 12:25:59 PDT 2013


On Thu, Aug 1, 2013 at 11:27 AM, Mark S. Miller <erights at google.com> wrote:
> There are three questions here, which need to be settled in roughly this
> chronological order:
> 1) What should tc39 do quickly, to unblock the DOM's need for promises and
> avoid a design fork?
> 2) What should DOM do quickly the tc39's quick output?
> 3) Once #1 and #2 are settled, what should tc39 do for es7?
>
> For #1 I agree with Tab. We should not reopen this issue, but should rather
> proceed to settle the AP2ish design quickly. Otherwise we won't settle
> anything quickly and DOM will go their own way.

And, importantly, except for the open question of thenable/branding,
our proposal is behaviorally and API-compatible with current DOM
promises.

> For #2, since whatever DOM does quickly becomes a compat constraint on all
> future decisions, DOM should take the minimum subset of #1 which actually
> meets their short term needs. I leave it to those who understand those needs
> to argue about what these are.

Unfortunately, the thenable question still impinges on the minimum subset. :/

~TJ


More information about the es-discuss mailing list