The Final ES2015 (ES6) Draft

http://wiki.ecmascript.org/doku.php?id=harmony:specification_drafts#final_draft

by kolodny • 11 years ago

144 72 11 years ago

wiki.ecmascript.org

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.

tragic3• 11 years ago

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.

But seriously: use Babel.

VeejayRampay3• 11 years ago

Oh absolutely Babel is awesome, just wondering.

cabirum2• 11 years ago

That's why MS gives out Win10 for free: there are zero reasons to stick with 7.

Touche5• 11 years ago

But seriously: use Babel.

Ugh, I find this to be excruciating. So you read about some new cool technology on HTML5Rocks and you want to play around with it. You have to:

* npm init

* npm install babel --save

* npm install browserify/webpack/greatest-thing-ever-of-the-week --save

* npm install gulp/grunt/broccoli/other-task-runner --save

* vi (gulp/grunt/broc/other)file.js

* Write some code to build your application.

* vi myapp.js (write some code to do your thing)

* > (gulp/grunt/broc) build

* Write an html file that includes your bundled es5.

* Open it in the browser. Yay! Cool I can debug now... wait a second I made a mistake.

* vi myapp.js and fix mistake.

* > (gulp/grunt/broc) build

* Oops I made another mistake. Better set up a watch-mode so I don't have to keep running build.

* npm install some-watch-thing --save

* vi (gulp/grunt/broc/other)file.js

* Add your watch code

* > (gulp/grunt/broc) watch

* Yay I can finally just fucking code now.

M2Ys4U2• 11 years ago

The browser-formerly-known-as-IE is currently running ahead of Chrome and FF on ES6 implementation

Not according to Kangax's table.[0] Both Fx 39 and 40 beat out Edge, with 65%, 66% and 63% respectively.

[0] https://kangax.github.io/compat-table/es6/

lewisl90292• 11 years ago

Or better yet, use jspm with Babel and use ES6 modules for everything.

https://github.com/jspm/jspm-cli

https://github.com/systemjs/systemjs

atirip2• 11 years ago

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.

tragic3• 11 years ago

That's an extraordinarily reductive view of improvements to a programming language. A basic example: cleaner syntax for anonymous functions will have (presumably) almost no effect on speed/memory either which way, but will make code more readable. Which is not a 'hipster' concern.

VeejayRampay3• 11 years ago

Upvoted your comment so that everyone can see it.

ES6 has template strings, destructuring assignment, Map and Set data structures (and more). While you're right and it is not NEEDED, this is something that dramatically improves on the weakest aspects of ECMASscript.

Based on your comment, it feels like no addition is ever a good addition if you can express it with the building bricks you already have. With such a way of seeing things, we'd all be coding with assembly language, cause nothing really affects speed or memory consumption for the better.

etimberg• 11 years ago

Map and set are much nicer in ES6 as built in objects.

realistschuckle• 11 years ago

Proxies. You can't shim in the Proxy object. Ain't no hipster feature there.

karoladamiec3• 11 years ago

One reason to rule them all: Generator functions.

Why it is a big deal one might ask. It is the BIGGEST deal in history of Javascript in my book because it allows you to do async that looks sync. No more callback hell. It is the single most important feature, as it eliminates async issues completely. And EVERYTHING in js is async. But in reality, you want to drop into async only sometimes. Now you are forced into it 100% time, even when you need the result of async call to decide what to do next. It gets tricky really fast.

madeofpalk2• 11 years ago

New Safari (in iOS 9 and next OS X) will support most of the ES 6 features. I guess it depends on what you're developing for.

robin_reala2• 11 years ago

Even the latest Webkit is only on 50% on Kangax’s support table. I suppose that’s better than latest Chrome (45%) but much worse than latest IE (63%) or latest Firefox (66%).

zghst4• 11 years ago

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.

[1] https://github.com/zloirock/core-js

sirsuki• 11 years ago

The Final ES1015 (ES6) Draft

Am I the only one noticing the oxymoron there?

netcraft• 11 years ago

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.

coldtea3• 11 years ago

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.

bsimpson• 11 years ago

And not long after this went up, the ECMA approved ES2015.

bshimmin• 11 years ago

I get documents from designers with names like "FINAL homepage v23 latest updated FINAL_2 (3).psd" all the time...

M8• 11 years ago

Expect the Final Final pre-Release post-Draft. ES6 will never get released.

M2Ys4U2• 11 years ago

It already is released: http://www.ecma-international.org/publications/standards/Ecm...

sago• 11 years ago

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.

pcwalton• 11 years ago

IIRC, the particular formatting in the document is required by ECMA and the ES6 committee can't do much about it.

bzbarsky2• 11 years ago

The right answer to the typography question is probably to just use the HTML version at http://people.mozilla.org/~jorendorff/es6-draft.html for all practical purposes.

The Final ES2015 (ES6) Draft

Related Stories