Promises: final steps
Mark S. Miller
erights at google.com
Thu Sep 5 06:11:44 PDT 2013
Thanks for posting this. I am also of the opinions that this fancy
developer tooling -- which I think is great and desperately needed anyway
-- will not substitute for the utility of .done. I expect we will
eventually decide to add .done back in. It expresses programmer intent in a
way that developer tooling cannot otherwise recover.
However, since we do not yet have experience with this tooling it is hard
to say. Given the purpose of this repository -- a minimal-ish compatible
subset of expected standard ES7 promises, adequate for DOM's immediate
needs -- we should leave .done out of this subset. Just as we are leaving
out many other features we expect will eventually be part of ES7 standard
On Thu, Sep 5, 2013 at 2:46 AM, medikoo <medikoo+mozilla.org at medikoo.com>wrote:
> While I can agree that "monitor" feature (that's proposed instead of
> has some benefits, I see it only as an aid for developers that are
> inexperienced with promises, or as a fallback for those experienced.
> It looks more as a smart add-on, which to be complete can't be implemented
> What's more important it still doesn't provide developer with full control
> I have problems understanding why such complex and not natural feature is
> favored over something so simple and straightforward.
> View this message in context:
> Sent from the Mozilla - ECMAScript 4 discussion mailing list archive at
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss