ECMAScript.next, "Harmony", ES6:

• the next version of ECMAScript
• improves on ECMAScript 5.1 Strict Mode
• the base for future JS implementations
• a project of ECMA's TC39 group
• a specification for engine implementors
• discussed in the open at es-discuss

ES6 goals:

• Be a better language for writing: complex applications, libraries (including DOM), code generators targeting it.
• A testable specification
• Improve interoperation, adopting de facto standards
• Support a statically verifiable, object-capability secure subset.

What ES (incl. 6) is NOT:

• a HTML / DOM / Networking / DB / System / Gfx / whatever API
• a solution for every problem ever imagined
• a language designed for the perfect world
• a way to make everybody happy
• a crowd-sourced project

What's in ES6?

• block scope, constants, destructuring,
• default args, rest, spread, => funs,
• syntax sugar: classes, a <| b, x.{ prop: val },
• generators (function*, yield)
• for...of loops, Maps, WeakMaps, Sets
• ...and more
• I talked about this at FrontRowConf :)

Some people aren't happy:

• feel the language evolves in the wrong direction
• feel TC39 isn't working in the open
• feel their (or "web developers'") ideas aren't heard by TC39

JSFixed

• Anton Kovalyov and Angus Croll launched JSFixed
• GitHub's issue tracker is used to discuss ideas and features, Google Moderator for voting
• Some ideas might be a nice addition, some are really weird
• Surprisingly, a few of these ideas are roughly the same as TC39's

JSFixed: What can you do?

• discuss the proposals at JSFixed
• vote for/against the proposals
• add your own proposals (not in this iteration?)

Before you start:

• try checking latest TC39's ES6 drafts
• browse es-discuss archives, maybe it was already thought of?
• is your idea generic enough to be part of the language? maybe it should only be in some API?

Will TC39 care?

• JSFixed team will document the good proposals & send them to TC39
• also, some es-discuss subscribers do read JSFixed issues
• need to overcome some bad feelings

So, does ES.next need to be fixed?

My opinion:

• Well, nothing is ever perfect...
• If JSFixed brings good ideas, that's awesome!
• ...and even if their ideas don't make it into ES6, it's still good to have more people knowing what's going on :)