Can we call it ECMAScript 6, yet?

Brendan Eich brendan at
Tue Sep 20 07:55:36 PDT 2011

On Sep 19, 2011, at 2:08 PM, OpenStrat at wrote:

> I think "further along" occurs when we have made final decisions on what is "in" and what is "not", because "not" starts to become "ES-Next",  What I would be afraid of is that "ES-6" is over populated with want-a-be's features and starts to get a life of its own (remember our experience with ES-3.1 and ES-4) and now we have ES-5 and some initial confusion like we don't know what we are doing.  There is no "rush" to name the next version (certainly nothing from the Ecma side).

If we know what we're doing, we do it. That was the purpose of the May cut-off on new proposals. We've been clear about the possibility of further cuts, but the

list is what stood after the cut-off.

Given the high overhead of creating a new edition and getting it through Ecma and then ISO, I don't think we can go "faster by doing less". If you know a way, I'm all ears. Otherwise I think we are "full" and just need editing and (more important) prototyping and user-testing time.

Doing the editing and prototyping/user-testing will shed new light. I expect not only cuts but a few adjustments and maybe an addition. So long as developers understand how this process works, I think it is ok to have a "what's *in* at this moment" understanding. Being coy about it, or vague as if we don't know enough, is not really square dealing in my view -- it doesn't help anyone. But this is separate from the "6" vs ".next" question.


> John
> In a message dated 9/19/2011 4:37:02 P.M. Eastern Daylight Time, allen at writes:
> On Sep 19, 2011, at 3:05 PM, Brendan Eich wrote:
> > 
> > You're right that the safer course is until we're further along. When is "further along" in your view?
> > 
> One approach is to not describe a features as "being in ES6"  until after it first appears in an actual ES6 draft.   From that perspective, what is currently "in" (or at least will be as soon as I upload a new draft) are let/const/function block scoped declarations, destructuring assignment/declarations/parameters, default parameter values, and the rest parameter. Probably a few other really minor things, too.
> Allen
> _______________________________________________
> es-discuss mailing list
> es-discuss at

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list