ES Discuss - Message History

Axel Rauschmayer (2015-01-22T22:07:52.000Z)

Go to Source

> The spec is no longer called ES6. The marketing hasn’t really begun to educate the community about this yet, but the spec is called ES 2015.

OK, good to know. Does it make sense to normally refer to it as “JavaScript 2015”, then?

> As for your concern about 2015 seeming old in 2016: **good**. In 2016, we’ll be publishing ES 2016, and ES 2015 will be missing a lot* of stuff that ES 2016 has!
> 
> * hopefully.

Even ignoring books, I don’t share that attitude: for programming languages, a slower pace is good. It took people a long time to get used to ES5 and ES 2015 will have many more new features. It will take time to:

* Completely implement ES 2015
* Write proper material
* Educate people
* Establish modules (I’m seeing browser APIs based on promises, but none that are based on modules)

Axel

-- 
Dr. Axel Rauschmayer
axel at rauschma.de
rauschma.de



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150122/c4d32ecb/attachment.html>

d at domenic.me (2015-02-13T23:22:58.482Z)

> The spec is no longer called ES6. The marketing hasn’t really begun to educate the community about this yet, but the spec is called ES 2015.

OK, good to know. Does it make sense to normally refer to it as “JavaScript 2015”, then?

> As for your concern about 2015 seeming old in 2016: **good**. In 2016, we’ll be publishing ES 2016, and ES 2015 will be missing a lot* of stuff that ES 2016 has!

Even ignoring books, I don’t share that attitude: for programming languages, a slower pace is good. It took people a long time to get used to ES5 and ES 2015 will have many more new features. It will take time to:

* Completely implement ES 2015
* Write proper material
* Educate people
* Establish modules (I’m seeing browser APIs based on promises, but none that are based on modules)

Axel

Edit