> > > I really don't know what to do about this. > > A few facts:
- Promises have a long history of controversy (I was there on the CommonJS list!) - The AP2 design was found acceptable (if not ideal) to all parties, providing us with a path through the controversy - Promises were a *very* late addition to ES6 With these facts at hand, the way forward seems clear: - Stick to AP2 like glue. - Sacrifice to deferment any non-fundamental part of the API which might re-ignite controversy. The committee failure mode of "do-both" should be stated more precisely as: "do-both at the expense of design coherency". AP2 is, in my opinion, a coherent design and therefore does not represent such a failure mode.
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
