A brief history of ECMAScript versions (including Harmony/ES.next)

DZone 's Guide to

A brief history of ECMAScript versions (including Harmony/ES.next)

· Web Dev Zone ·
Free Resource
Two questions:
  • What is the difference between JavaScript and ECMAScript?
  • What is the difference between ECMAScript Harmony and ECMAScript.next?
Both are almost trick questions, because in each case, the two terms mean basically the same. This post explains the details.


  • ECMAScript: Sun (now Oracle) had a trademark on the name “JavaScript” (which led to Microsoft calling its JavaScript dialect “JScript”). Thus, when it came to standardizing the language, a different name had to be used. Instead, “ECMAScript” was chosen, because the corresponding standard is hosted by Ecma International (see below). In practice, the terms “ECMAScript” and “JavaScript” are interchangeable. If JavaScript means “ECMAScript as implemented by Mozilla and others” then the the former is a dialect of the latter. The term “ECMAScript” is also frequently used to denote 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.
  • 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. The current goal is to have ECMAScript.next finished by 2013, with parts of it making it into web browsers (especially Firefox) before then.
  • ECMAScript is the “standard name” of the JavaScript language.
  • ECMAScript.next is the version after ECMAScript 5. ECMAScript Harmony is a superset of ECMAScript.next that additionally includes features to be considered after ECMAScript.next.
Sources and related reading:
  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

From http://www.2ality.com/2011/06/ecmascript.html

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}