First we have to wait for complete implementations.<p>Then wait for v8 performance: <a href="http://jsperf.com/performance-frozen-object" rel="nofollow">http://jsperf.com/performance-frozen-object</a> ES5 is doing good...<p>And at last: Wait for < IE-11 to die.<p>It remains to be seen if io.js will boosts ES Next for the server.
Since bound to v8 i don't expect much.<p>Other implementations like the ahead of time compiler echojs become interesting. I am also curious how Typescript will look at v2.0.<p>I am ready, however I still don't use arrow functions... Which were first heard of in 2010? 2011?<p>It still feels like so far away.
I'm sorry most of the sugar I don't find particularly helpful and can be confusing when you have more than one way to do something. generators, async keyword these should be prioritized not class based inheritance. Even block scoping I mean maybe I'm nuts but function scoping if you take the time to understand it, it works.
Being able to (eventually) use all these language features in a language that's running inside a browser is blowing my mind right now. It's got iterators! It's got properties!
State of ECMAScript-6 support in current browsers:<p><a href="http://kangax.github.io/compat-table/es6/" rel="nofollow">http://kangax.github.io/compat-table/es6/</a>
It looks like a 2nd system effect to me or a cancer of the features.<p>In JS there are a lot of other stuff to fix before adding syntax. (non commutativity of ==).<p>But adding stuff like macro, confusing multiline chars it looks like a hell to maintain to me.<p>Hours of painfully finding what could have triggered the bug!<p>The code? The macro? Is this a ' or a ` ? ....<p>Hell, this is hell coming on us my fellow grunt programmers.