It is so good to see ES moving again, after a decade in the wilderness. EC5 wasn't an aberration, and there are lots of productivity improvements in this and coming in ES7. A big thankyou and congratulations to the people who worked so hard on this. The work of a standardisation committees is often a thankless task.
On a slightly churlish note, the typography / graphic design of the standardisation document is absolutely horrid. From the color choices, to the (many) fonts, to the early 90s type treatment to the fake laid paper texture on the cover to inconsistent spacing inside. Shiver. Okay, superficial, but only slightly so. I genuinely think that type and book design is important for communication.
If someone in the know could give me a rough estimate of "When can I expect to be using ES6 to develop applications (at least for modern browsers)?", that'd be nice.
And I'm not talking Babel or any other tools like that, I'm talking straight up ES6.
A good while yet, I'd expect; a lot depends on Windows 10 uptake. The browser-formerly-known-as-IE is currently running ahead of Chrome and FF on ES6 implementation, but if everyone sticks with Win7 for the next half decade it won't amount to much.
I am confident full ES6 support will be really solid by March 2017. However, the community is moving incredibly fast, some companies are already using ES7 / ES2016 features!
In perspective, transpilers aren't so bad, especially Babel, who's differentiating feature from the start was readable output code.
Today, if targeting modern browsers you can use Maps and Sets. With polyfills[1] you can use the new Array functions, Promises, Symbols, full JS collections, iterators, etc.
Why? What is the thing you can do in ES6 that you can't in ES5? Features that affect execution speed or real memory consumption positively. Leave hipster features out.
No. "Final Draft" is a very standard term in books/scripts/standards/legal docuemnts/etc (actually there's even a scriptwriting app bearing that name).
It's the final draft as in "the last in the series of draft revisions", meaning than after that the actual standard document is going to be voted / published -- at worse with very minor last minute corrections.
I believe thats exactly what it is - the latest revision of the document that will go on to be voted on and accepted.
>This draft has been submitted to the Ecma General Assembly members for their review and consideration. The GA will vote on approving it as a Ecma standard at their June 2015 meeting.
>Assuming GA approval, it will still be possible to make very minor editorial corrections in the published version.
[+] [-] sago|10 years ago|reply
On a slightly churlish note, the typography / graphic design of the standardisation document is absolutely horrid. From the color choices, to the (many) fonts, to the early 90s type treatment to the fake laid paper texture on the cover to inconsistent spacing inside. Shiver. Okay, superficial, but only slightly so. I genuinely think that type and book design is important for communication.
[+] [-] bzbarsky|10 years ago|reply
[+] [-] pcwalton|10 years ago|reply
[+] [-] VeejayRampay|10 years ago|reply
And I'm not talking Babel or any other tools like that, I'm talking straight up ES6.
[+] [-] tragic|10 years ago|reply
But seriously: use Babel.
[+] [-] madeofpalk|10 years ago|reply
[+] [-] zghst|10 years ago|reply
In perspective, transpilers aren't so bad, especially Babel, who's differentiating feature from the start was readable output code.
Today, if targeting modern browsers you can use Maps and Sets. With polyfills[1] you can use the new Array functions, Promises, Symbols, full JS collections, iterators, etc.
[1] https://github.com/zloirock/core-js
[+] [-] unknown|10 years ago|reply
[deleted]
[+] [-] atirip|10 years ago|reply
[+] [-] sirsuki|10 years ago|reply
Am I the only one noticing the oxymoron there?
[+] [-] coldtea|10 years ago|reply
It's the final draft as in "the last in the series of draft revisions", meaning than after that the actual standard document is going to be voted / published -- at worse with very minor last minute corrections.
[+] [-] netcraft|10 years ago|reply
>This draft has been submitted to the Ecma General Assembly members for their review and consideration. The GA will vote on approving it as a Ecma standard at their June 2015 meeting.
>Assuming GA approval, it will still be possible to make very minor editorial corrections in the published version.
[+] [-] bshimmin|10 years ago|reply
[+] [-] M8|10 years ago|reply