Play fair now. SpiderMonkey in Firefox prototyped let, const,
generators, iterators (an earlier form), destructuring (close to final
ES6), comprehensions, generator expressions, and more recently proxies,
weak maps, maps, and sets. V8 joined in the proxies, weak maps, maps,
and sets fun. The for-of loop from ES6 is in SpiderMonkey now. Most
significantly, modules are under way in SpiderMonkey and V8.
We prototype as we go. V8 has kept stuff under a flag and that's fair --
we may do likewise, certainly with new stuff likely to change, in
SpiderMonkey. But saying nothing is coming out of TC39 is inaccurate.
If you mean classes are not being prototyped because 'const class' or
equivalent is not part of the almost-at-consensus "maximally minimal
classes" strawman, you're right. If we must have a way to fix the
properties of a class instance as Waldemar wishes, then I predict
classes won't be in ES6 and it will be hard to justify prototyping less
than the full required (as yet unwritten) proposal that satisfies
everyones' wants.
That is a shame, and a stain on TC39's escutcheon. But you should be
accurate about the many other things we have done, which are coming along.
/be
Brandon Benvie wrote:
The last discussion point there is really important I think. I get a
strong sense of the general JS developer world feeling no connection
at all to this process, and much can be put directly on the sheer
timescale. We've seen 2 month browser version cycles come in force,
the "living standard" that is HTML5 and the as of recent rapid
movement of new APIs coming out to JS from not-TC39. People don't feel
connected to the things in ES6 because they rightfully can't envision
using them in an imaginable timeframe.
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
