ECMAScript.next features are taking shape
ECMAScript.next features are taking shape
Join the DZone community and get the full member experience.
Join For FreeLearn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.
The ECMAScript wiki has two pages with features that might make it into ECMAScript.next:
- Harmony proposals: Features that browser vendors (in the TC39 [2]) agreed should be part of ECMAScript.next. Highlights:
- Destructuring assignment
- Iterators
- Generators
- Modules
- Strawman: Proposals where TC39 is still debating whether to include them in ECMAScript.next or not. Quoting a tweet by Brendan Eich:
See [the Strawman page] for “not yet Harmony but maybe ES.next.next”. A few of these should still make ES.next...
Examples:- Shorter function syntax
- Data structures: maps, sets, ...
- Class abstractions
- Paren-free syntax
- More blog posts on ECMAScript.next: ecmascript.next.
- ECMA, TC-39, and Bears - Oh My!
From http://www.2ality.com/2011/04/ecmascriptnext-features-are-taking.html
What’s the best way to boost the efficiency of your product team and ship with confidence? Check out this ebook to learn how Sentry's real-time error monitoring helps developers stay in their workflow to fix bugs before the user even knows there’s a problem.
Like This Article? Read More From DZone
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}