ECMAScript 2015 Approved
ecma-international.org
ECMAScript 2015 Approved
1–10 of 108 posts
Re: ECMAScript 2015 Approved
#2They are providing a official HTML version, alongside the PDF version.
Re: ECMAScript 2015 Approved
#3FYI, ECMAScript 2015 is also known as ES6.
Re: ECMAScript 2015 Approved
#4Can someone explain what this means for the browser ecosystem? What are the next steps to integration?
Re: ECMAScript 2015 Approved
#5FYI, ECMAScript 2015 is also known as ES6.
And JavaScript Harmony
Re: ECMAScript 2015 Approved
#6Can someone explain what this means for the browser ecosystem? What are the next steps to integration?
It's underway already. Check out Kangax's amazing work here [0]
[0] ES6 COMPAT TABLE: https://kangax.github.io/compat-table/es6/
Re: ECMAScript 2015 Approved
#7FYI, ECMAScript 2015 is also known as ES6.
Because of their switch to use a year instead of a version number, do they plan on doing these ES enhancements more often?
Re: ECMAScript 2015 Approved
#8Can someone explain what this means for the browser ecosystem? What are the next steps to integration?
I think it means we can now pine over EcmaScript 7.
Re: ECMAScript 2015 Approved
#9Can someone explain what this means for the browser ecosystem? What are the next steps to integration?
I think it means we can now pine over EcmaScript 7.
Don't pine, just use Babel ;) http://kangax.github.io/compat-table/es7/
Re: ECMAScript 2015 Approved
#10Can someone explain what this means for the browser ecosystem? What are the next steps to integration?
Depending on the browser, lots of things are already implemented, either generally available (e.g. `Promise`) or behind flags (e.g. fat arrows). This announcement just accelerates the adoption pipeline by reducing worry about spec changes.