## Pages

- Home
- About
- Best of
- Subscribe
- Advertise

Upcoming: my programmer’s guide to JavaScript (free online).

## 2011-06-27

### ECMAScript: ES.next versus ES 6 versus ES Harmony

Labels: dev, esnext, javascript, jslang
Update 2011-04-18: Rewrote this blog post, renamed it from “A brief history of ECMAScript versions (including Harmony and ES.next)”.

This blog post explains the difference between JavaScript and ECMAScript. And the differences between ECMAScript.next, ECMAScript 6 and ECMAScript Harmony.

### A little ECMAScript glossary

You should know the following terms related to the standardization of JavaScript.

- ECMAScript: Sun (now Oracle) had a trademark on the name “Java” and therefore also on the name “JavaScript”. That led to Microsoft calling its JavaScript dialect “JScript”. Thus, when it came to standardizing the language, a different name had to be used. “ECMAScript” was chosen, because the corresponding standard is hosted by Ecma International (see below). Usually, the terms “ECMAScript” and “JavaScript” are interchangeable. If JavaScript means “ECMAScript as implemented by Mozilla and others” then ECMAScript is the standard and JavaScript its implementation. The term “ECMAScript” is also used to describe language versions (such as ECMAScript 5).
- ECMA-262: The Ecma International (a standards organization) has created the ECMA-262 standard which is the official specification of the ECMAScript language.
- ECMAScript 5: If one talks about ECMAScript 5, one means the 5th edition of ECMA-262, the current edition of this standard.
- Ecma’s Technical Committee 39 (TC39): is the group of people (Brendan Eich and others) who develop the ECMA-262 standard.

### History of ECMAScript versions

The following are the most currently relevant chapters in ECMAScript’s history:

- ECMAScript 3 (December 1999). This is the version of ECMAScript that most browsers support today. It introduced many features that have become an inherent part of the language:

  > [...] regular expressions, better string handling, new control statements, try/catch exception handling, tighter definition of errors, formatting for numeric output and other enhancements. [1]

- ECMAScript 4 (abandoned July 2008). ECMAScript 4 was developed as the next version of JavaScript, with a prototype written in ML. However, TC39 could not agree on its feature set. To prevent an impasse, the committee met at the end of July 2008 and came to an accord, summarized in four points [2]:
  1. Develop an incremental update of ECMAScript (which became ECMAScript 5).
  2. Develop a major new release, which was to be more modest than ECMAScript 4, but much larger in scope than the version after ECMAScript 3. This version has been code-named Harmony, due to the nature of the meeting in which it was conceived.
  3. Features from ECMAScript 4 that would be dropped: packages, namespaces, early binding.
  4. Other ideas were to be developed in consensus with all of TC39.
  Thus: The ECMAScript 4 developers agreed to make Harmony less radical than ECMAScript 4, the rest of TC39 agreed to keep moving things forward.
- ECMAScript 5 (December 2009). This version brings several enhancements to the standard library and even updated language semantics via a strict mode. [3]
- ECMAScript.next (planned for 2013). It quickly became apparent that the plans for Harmony were too ambitious, so its features were split into two groups: Group one are features that are considered for the next version after ECMAScript 5. This version has the code name ECMAScript.next and will probably become ECMAScript 6. Group two are Harmony features that are not considered ready or high-priority enough for ECMAScript.next. Those will still make it into ECMAScript, e.g. as part of ECMAScript.next.next. The current goal is to have ECMAScript.next finished by 2013, with parts of it making it into web browsers (especially Firefox) before then.

### Summary

ECMAScript versus JavaScript. ECMAScript is the language standard. JavaScript is one implementation, Microsoft’s JScript is another one.

Upcoming versions of ECMAScript:

- ECMAScript.next is the code name of the next version of ECMAScript. Using that term implies that one is discussing features that may or may not be added to the final standard.
- ECMAScript 6 is the actual (final) name of ECMAScript.next. Using that term implies that one is talking about features that will definitely be in the standard.
- ECMAScript Harmony is a superset of ECMAScript.next and means “features coming up after ECMAScript 5”. Those features may be in ECMAScript.next, in ECMAScript.next.next or in even later versions.

### References

1. ECMAScript - Wikipedia, the free encyclopedia
2. ECMAScript Harmony (archived email)
3. What’s new in ECMAScript 5
4. JavaScript: how it all began
5. Posts on ECMAScript.next
   - Best overview of planned features: “ECMAScript.next: the ‘TXJS’ update by Eich”

#### 3 comments:

Allen Wirfs-Brock said...

  A few clarify notes:
  The members of Ecma International and TC-39 are actually organizations such as Mozilla and Microsoft. Individual who attend meetings are doing so as representatives of those organizations
  Work on "ES4" started even before completion of ES3. It was a on-again/off-again effort and there were fairly complete "ES4" drafts that predated the work that was abandoned in 2008.
  The current Ecma-262 standard is actually Edition 5.1 which was published in June 2011. ES5.1 makes editorial and technical corrections to ES5 but adds no new features. The ES5.1 specification is also published as an ISO standard which is known as ISO/IEC 16262:2011.
  Microsoft seems to be de-emphasizing the JScript name and informally seems to call the language JavaScript just like everybody else.
  Whether or not ECMAScript 6 is the actual final name of the next major revisions of ECMAScript remains to be seen (note ES 4 history). We are far enough along in drafting that specification but that ES 6 seems like a safe bet nothing is sure until it is published.
  Allen Wirfs-Brock
  Mozilla
  Ecma-262 Project Editor

  April 18, 2012 at 9:13 PM
Axel Rauschmayer said...

  Thanks Allen, much appreciated! Will work these into the post, eventually.

  April 18, 2012 at 9:42 PM
Aaronfrost said...

  Axel, just a great explanation here. Thank you! I might come back to you one day to cite you on a few of these pieces. Thank you!

  April 20, 2012 at 9:22 PM

####

Newer Post Older Post Home
Subscribe to: Post Comments (Atom)