JavaScript 2015?

nw at nw at
Thu Jan 22 21:04:41 PST 2015

I bet hipsters will drop the "20" for a shorter name, ES15 ;)

I feel your pain Axel. I have been helping out with a lot of web boot camps lately teaching newcomers web technologies. Trying to explain all this is a real mess. Many developers I know that passively touch JS daily at work are unfamiliar, confused or frightened by the ES terminology still! At least with JS/ES you can explain clear iterations even if vendors haven't fully adopted. Living specs like HTML5 are almost impossible for newcomers to grasp, it's kinda sad. 

Axel, I look forward to your book regardless of the title. It's refreshing to see someone care about educating people on proper nomenclature. Heck, it looks like this thread could be a chapter defining the mess that is web technologies :-)  

> On Jan 22, 2015, at 9:19 PM, Domenic Denicola <d at> wrote:
> From: es-discuss [mailto:es-discuss-bounces at] On Behalf Of Axel Rauschmayer
>> I don’t care what ES7 is called, but I have to decide soon on what to put on the cover of an ES6 book and that cover will either be inspired by a 6 or by a 2015.
> ES 2015 is the official name of the spec. Various people will probably still call it ES6 for a while. (I know it hasn't become automatic for me to type yet.) It might be hard for your readers to Google and find the official spec if you use "ES6", but they'll probably find other resources more readily, at least for now.
> In general I think you're in trouble if you're trying to tie your book marketing to version numbers. _Maybe_ naming a book after, say, C# 5 makes sense, since C# is essentially bundled with single-vendor Visual Studio releases and each version is implemented all at once. But even then, the old books I have on my bookshelf are named things like "C# in Depth" and "More Effective C#," and get edition updates as Microsoft spins out new versions. For the web, such a naming scheme makes even less sense. Features on the web are implemented piecemeal from draft specifications and/or living standards, and updated over time, and there is never a cross section of ES you can point to in real-world implementations and say "this is ES 2015". 
> Books purporting to cover "HTML5" or "CSS3" are a joke. The same is true for ES 2015, or ES 2016.
> _______________________________________________
> es-discuss mailing list
> es-discuss at

More information about the es-discuss mailing list