I still cannot understand how, in 2015, the ECMAScript spec is maintained by Allen Wirfs-Brock as a Word document. In their (partial) defense, a TC-39 member explained to me how it's been "good enough" up to now and that for ES7 they want to move to a plain-text based source format from which publishable versions can get generated.

I don't know of any TC39 member who thinks it's "good enough". It's my personal top-priority to leave Word behind as soon as ES6 is shipped.

Here's an interesting script in the TypeScript repo that may be of use: https://github.com/Microsoft/TypeScript/blob/master/scripts/...

Something else from the same repo that may also be of use: TypeScript's elegant and well-considered type system... wink wink

A quick look at the compiled script

        var fileStream = new ActiveXObject("ADODB.Stream");

shows that the script seems to depend on Windows plateform.

It does, yes. See the comment at the top of the file: It requires cscript.exe, which is more or less just the Windows Script Host.

I pointed out the script ostensibly because of the similarities of ES6 and TypeScript both having specs written in Word, and of a desire to convert into a much more web-friendly format. See specs.md: https://github.com/Microsoft/TypeScript/tree/master/doc

Speaking more honestly, I was being a bit tongue-in-cheek and trying to bounce certain eyes onto the TypeScript repo in the continued hopes that its transparent, optional, gradual type system be further considered for future versions of ES (such as 7...wink?)

Same reason a lot of people use Word, revision tracking. Its the killer feature. Source code control, if it were for the normal person, could work but it would need some editor integrated tooling to show all the changes in place.

If you want to replace Word, make this your first and focused feature. The easy, no distraction writing folks are already numerous and successful for their niche.

Wikis have revision tracking and at least they have a global version rather than "document v2 from Bob final8 really (with corrections).docx"

Also wikis are as distraction free as it gets...

I haven't seen a wiki with as good and editor as a standard word processor, also I'm not sure they are as distraction free and the current crop of distraction free apps like Scrivener and WriteRoom.

VoodooPad probably qualifies as a wiki / word processor fusion that works really well for writing.

Why not the web?

The generated version at https://people.mozilla.org/~jorendorff/es6-draft.html normally follows very close behind the latest drafts.

(Side-note: I typically only reference the web version of the ES5 spec also @ http://es5.github.io/ ).

Which is made with this: https://github.com/jorendorff/es-spec-html if you really need it in HTML format :)

It's a race to implement. Looks as if Mozilla is going to get there first. But, I wouldn't be surprised if Spartan/Chakra ended up surprising us with full support when it's released. https://kangax.github.io/compat-table/es6/

It would certainly be a trip to switch back to a Microsoft browser as my main webdev tool if that does happen.

No Linux support would be a big downside.

Also, they would have to work tremendously on the dev tools. IE dev tools in the present form are not very good, compared to Chrome Dev tools, or FF's dev edition (with Web IDE etc.).

Is there any estimated time for the release of the final version?

I read somewhere AngularJS 2.0 is expected to the end of this year, so I suppose that ES6 should be closed first.

By the way AngularJS 2.0 based on Typescript not ES6.

It's not clear on what angular 2.0 will be based, the more the angular team talks the unclearer it is :

http://i.imgur.com/upcrFbi.png

this is a slide from ngconf.

Yeah that slide is a little confusing because they messed up the second step. JS Facade is supposed to be where Dart Facade is and vice versa.

Also, Angular 2.0 is going to be written in TypeScript (which will be compiled to plain JS) but you can use ES5, ES6, TypeScript or Dart depending on what you want to use for your application.

TypeScript could be compiled to ES5 and ES6 (--target ES6).

what exactly is difference between ES.next and Harmony?

They differ in spelling and pronunciation.

ES.next and Harmony and ES6 are all old names for what is currently supposed to be referred to as ES2015

It's all a big mess

really!!!..are we expecting standards to ES every year?