On Feb 18, 2014, at 11:52 AM, Ehsan Akhgari <[email protected]> wrote:
>> The current ES6 consensus needs to be nailed down harder, but I think it >> will stick. That it isn't compositional won't stop this. Promises were a >> library de-facto standard from CommonJS and other ecosystems; the >> committee erred in trying to redesign them, the long email threads both >> before and after make this clear. > > So, what happens if we end up shipping what we have now, and then TC39 > propose another change to the spec? We won't, for the reasons I just gave cited above. Plus, we are out of time. > Right now Blink is in that same situation where they have something shipped > which no longer conforms to the spec, and they don't know for a fact whether > the current ES6 consensus is going to stick for sure, so they're unwilling to > update their implementation out of the fear of having to adjust it again > later on for further changes. Beware the confounding variable that the v8 principal dissents about the current and IMHO final consensus. Let's track the spec, please. Allen and Jason should say what is in the spec and stable. /be _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
