Paradigm Multi-paradigm: prototype-based, functional, imperative
Designed by Brendan Eich, Ecma International
First appeared 1997 (1997)
Typing discipline weak, dynamic
Major implementations
JavaScript, SpiderMonkey, V8, ActionScript, JScript, QtScript, InScript
Influenced by
Self, HyperTalk, AWK, C, Perl, Python, Java, Scheme
Filename extensions .es
Internet media type application/ecmascript
Developed by Sun Microsystems,
Ecma International
Initial release June 1997 (1997-06)
Latest release
Edition 7
(June 17, 2016 (2016-06-17))
Type of format Scripting language
Website ECMA-262, ECMA-290,
ECMA-327, ECMA-357,

ECMAScript (or ES)[1] is a trademarked[2] scripting-language specification standardized by Ecma International in ECMA-262 and ISO/IEC 16262. It was based on JavaScript, which now tracks ECMAScript. It is commonly used for client-side scripting on the World Wide Web. Other implementations of ECMAScript include JScript and ActionScript.


The ECMAScript specification is a standardized specification of a scripting language developed by Brendan Eich of Netscape; initially it was named Mocha, later LiveScript, and finally JavaScript.[3] In December 1995, Sun Microsystems and Netscape announced JavaScript in a press release.[4] In March 1996, Netscape Navigator 2.0 was released, featuring support for JavaScript.

Owing to the widespread success of JavaScript as a client-side scripting language for Web pages, Microsoft developed a compatible dialect of the language, naming it JScript to avoid trademark issues. JScript added new date methods to alleviate the Year 2000 problem caused by the JavaScript methods that were based on the Java Date class.[5] JScript was included in Internet Explorer 3.0, released in August 1996.

Netscape delivered JavaScript to Ecma International for standardization and the work on the specification, ECMA-262, began in November 1996.[6] The first edition of ECMA-262 was adopted by the Ecma General Assembly in June 1997. Several editions of the language standard have been published since then. The name "ECMAScript" was a compromise between the organizations involved in standardizing the language, especially Netscape and Microsoft, whose disputes dominated the early standards sessions. Eich commented that "ECMAScript was always an unwanted trade name that sounds like a skin disease."[7]

While both JavaScript and JScript aim to be compatible with ECMAScript, they also provide additional features not described in the ECMA specifications.[8]


There are seven editions of ECMA-262 published. Work on version 7 of the standard, was finalized in June 2016.[9]

Edition Date published Changes from prior edition Editor
1 June 1997 First edition Guy L. Steele Jr.
2 June 1998 Editorial changes to keep the specification fully aligned with ISO/IEC 16262 international standard Mike Cowlishaw
3 December 1999 Added regular expressions, better string handling, new control statements, try/catch exception handling, tighter definition of errors, formatting for numeric output and other enhancements Mike Cowlishaw
4 Abandoned Fourth Edition was abandoned, due to political differences concerning language complexity. Many features proposed for the Fourth Edition have been completely dropped; some are proposed for ECMAScript Harmony.
5 December 2009 Adds "strict mode," a subset intended to provide more thorough error checking and avoid error-prone constructs. Clarifies many ambiguities in the 3rd edition specification, and accommodates behaviour of real-world implementations that differed consistently from that specification. Adds some new features, such as getters and setters, library support for JSON, and more complete reflection on object properties.[10] Pratap Lakshman, Allen Wirfs-Brock
5.1 June 2011 This edition 5.1 of the ECMAScript Standard is fully aligned with third edition of the international standard ISO/IEC 16262:2011. Pratap Lakshman, Allen Wirfs-Brock
6 June 2015[11] The Sixth Edition, known as ES6 or ECMAScript 2015,[11] adds significant new syntax for writing complex applications, including classes and modules, but defines them semantically in the same terms as ECMAScript 5 strict mode. Other new features include iterators and for/of loops, Python-style generators and generator expressions, arrow functions, binary data, typed arrays, collections (maps, sets and weak maps), promises, number and math enhancements, reflection, and proxies (metaprogramming for virtual objects and wrappers). As the first "ECMAScript Harmony" specification, it is also known as "ES6 Harmony." Allen Wirfs-Brock
7 June 2016[12] The Seventh Edition intended to continue the themes of language reform, code isolation, control of effects and library/tool enabling from ES6, includes two new features: the exponentiation operator (**) and Array.prototype.includes. Brian Terlson
8 New features proposed include concurrency and atomics, zero-copy binary data transfer, more number and math enhancements, syntactic integration with promises, observable streams, SIMD types, better metaprogramming with classes, class and instance properties, operator overloading, value types (first-class primitive-like objects), records and tuples, and traits.[13][14]

In June 2004, Ecma International published ECMA-357 standard, defining an extension to ECMAScript, known as ECMAScript for XML (E4X). Ecma also defined a "Compact Profile" for ECMAScript – known as ES-CP, or ECMA 327 – that was designed for resource-constrained devices, which was withdrawn in 2015.[15]

4th Edition (abandoned)

The proposed fourth edition of ECMA-262 (ECMAScript 4 or ES4) would have been the first major update to ECMAScript since the third edition was published in 1999. The specification (along with a reference implementation) was originally targeted for completion by October 2008.[16] An overview of the language was released by the working group on October 23, 2007.[17]

By August 2008, the ECMAScript 4th edition proposal had been scaled back into a project codenamed ECMAScript Harmony. Features under discussion for Harmony at the time included

The intent of these features was partly to better support programming in the large, and to allow sacrificing some of the script's ability to be dynamic to improve performance. For example, Tamarin – the virtual machine for ActionScript developed and open sourced by Adobe – has just-in-time compilation (JIT) support for certain classes of scripts.

In addition to introducing new features, some ES3 bugs were proposed to be fixed in edition 4.[18][19] These fixes and others, and support for JSON encoding/decoding, have been folded into the ECMAScript, 5th Edition specification.[20]

Work started on Edition 4 after the ES-CP (Compact Profile) specification was completed, and continued for approximately 18 months where slow progress was made balancing the theory of Netscape's JavaScript 2 specification with the implementation experience of Microsoft's JScript .NET. After some time, the focus shifted to the ECMAScript for XML (E4X) standard. The update has not been without controversy. In late 2007, a debate between Eich, later the Mozilla Foundation's CTO, and Chris Wilson, Microsoft's platform architect for Internet Explorer, became public on a number of blogs. Wilson cautioned that because the proposed changes to ECMAScript made it backwards incompatible in some respects to earlier versions of the language, the update amounted to "breaking the Web,"[21] and that stakeholders who opposed the changes were being "hidden from view".[22] Eich responded by stating that Wilson seemed to be "repeating falsehoods in blogs" and denied that there was attempt to suppress dissent and challenged critics to give specific examples of incompatibility.[23] He also pointed out that Microsoft Silverlight and Adobe AIR rely on C# and ActionScript 3 respectively, both of which are larger and more complex than ECMAScript Edition 3.[24]

5th Edition

Yahoo, Microsoft, Google, and other 4th edition dissenters formed their own subcommittee to design a less ambitious update of ECMAScript 3, tentatively named ECMAScript 3.1. This edition would focus on security and library updates with a large emphasis on compatibility. After the aforementioned public sparring, the ECMAScript 3.1 and ECMAScript 4 teams agreed on a compromise: the two editions would be worked on, in parallel, with coordination between the teams to ensure that ECMAScript 3.1 remains a strict subset of ECMAScript 4 in both semantics and syntax.

However, the differing philosophies in each team resulted in repeated breakages of the subset rule, and it remained doubtful that the ECMAScript 4 dissenters would ever support or implement ECMAScript 4 in the future. After over a year since the disagreement over the future of ECMAScript within the Ecma Technical Committee 39, the two teams reached a new compromise in July 2008: Brendan Eich announced that Ecma TC39 would focus work on the ECMAScript 3.1 (later renamed to ECMAScript, 5th Edition) project with full collaboration of all parties, and vendors would target at least two interoperable implementations by early 2009.[25][26] In April 2009, Ecma TC39 published the "final" draft of the 5th edition and announced that testing of interoperable implementations was expected to be completed by mid-July.[27] On December 3, 2009, ECMA-262 5th edition was published.[28]

6th Edition - ECMAScript 2015

The 6th edition, officially known as ECMAScript 2015, was finalized in June 2015.[11][29][9] This update adds significant new syntax for writing complex applications, including classes and modules, but defines them semantically in the same terms as ECMAScript 5 strict mode. Other new features include iterators and for/of loops, Python-style generators and generator expressions, arrow functions, binary data, typed arrays, collections (maps, sets and weak maps), promises, number and math enhancements, reflection, and proxies (metaprogramming for virtual objects and wrappers).[30][31] The complete list is extensive.[32]

Browser support for ES6 is still incomplete.[33] However, ES6 code can be transpiled into ES5 code, which has more consistent support across browsers. [34] Transpiling adds an extra step to build processes whereas polyfills allow adding extra functionalities by including another javascript file.

7th Edition - ECMAScript 2016

The 7th edition, officially known as ECMAScript 2016, was finalized in June 2016.[12] New features include the exponentiation operator (**) and Array.prototype.includes.


ES.Next is a dynamic name that refers to whatever the next version is at time of writing. ES.Next features are more correctly called proposals, because by definition the specification has not been finalized yet.


The ECMAScript language includes structured, dynamic, functional, and prototype-based features.[35]


Main article: ECMAScript syntax


ECMAScript is supported in many applications, especially Web browsers, where it is implemented by JavaScript, or, in the case of Internet Explorer, JScript. Implementations sometimes include extensions to the language, or to the standard library and related application programming interfaces (API) such as the World Wide Web Consortium (W3C) specified Document Object Model (DOM). This means that applications written in one implementation may be incompatible with another, unless they are written to use only a common subset of supported features and APIs.

Implementation Applications ECMAScript edition
SpiderMonkey Firefox, the Gecko layout engine, Adobe Acrobat[d 1] 5.1, and features from 6 and 7[d 2]
V8 Google Chrome, Node.js, Opera, MarkLogic.[36] 6[d 3]
JavaScriptCore (Nitro) WebKit, Safari, Qt 5 6[37]
Chakra Microsoft Edge 5.1, and features from 6[d 4]
JerryScript Resource constrained IoT devices, Pebble 5.1[38]
JScript 9.0 Internet Explorer, the Trident layout engine 5.1
Nashorn Java 5.1[39]
Rhino Java Platform, Standard Edition 3
Carakan (deprecated) Opera 12 5[d 5][d 6]
KJS KHTML 5.1 and features from 6
Ejscript Appweb Web Server, Samba 4 6[40]
JScript .NET Microsoft .NET Framework 3[d 7]
ActionScript Adobe Flash, Adobe Flex, Adobe AIR 4[41]
ExtendScript Adobe Creative Suite products: InDesign, Illustrator, Photoshop,
Bridge, After Effects, Premiere Pro
InScript iCab 3
Max/MSP engine Max 3
QtScript (deprecated) KDE SC 4 3
Caja 5[42]
  1. Adobe Acrobat 9.0 uses the SpiderMonkey 1.7 engine: JavaScript for Acrobat API Reference
  2. ECMAScript 6 support in Mozilla and ECMAScript 7 support in Mozilla
  3. Chrome has already supported majority of ECMAScript 2015 features. According to the widely used compatibility table, Chrome 52 has passed all tests when experimental JavaScript flag is on.
  4. Microsoft states that Edge "supports most ES2015 features," supporting 81% of the specification as of May 2015 and 93% as of November 2016.
  5. Full ECMAScript 5.1 support in Opera 11.51+.
  6. Opera's implementation includes some JavaScript and JScript extensions: ECMAScript support in Opera Presto 2.3
  7. Microsoft asserts that JScript 8.0 supports "almost all of the features of the ECMAScript Edition 3 Language Specification", but does not list the unsupported features.

Version correspondence

Items on the same line are approximately the same language.[43][44]

JavaScript JScript ECMAScript
1.0 (Netscape 2.0, March 1996) 1.0 (IE 3.0 – early versions, August 1996)
1.1 (Netscape 3.0, August 1996) 2.0 (IE 3.0 – later versions, January 1997)
1.2 (Netscape 4.0-4.05, June 1997)
1.3 (Netscape 4.06-4.7x, October 1998) 3.0 (IE 4.0, Oct 1997) Edition 1 (June 1997) / Edition 2 (June 1998)
1.4 (Netscape Server only) 4.0 (Visual Studio 6, no IE release)
5.0 (IE 5.0, March 1999)
5.1 (IE 5.01)
1.5 (Netscape 6.0, Nov 2000; also
later Netscape and Mozilla releases)
5.5 (IE 5.5, July 2000) Edition 3 (December 1999)
5.6 (IE 6.0, October 2001)
1.6 (Gecko 1.8, Firefox 1.5, November 2005) Edition 3, with some compliant enhancements: ECMAScript for XML (E4X), Array extras (e.g. Array.prototype.forEach), Array and String generics (New in JavaScript 1.6)
1.7 (Gecko 1.8.1, Firefox 2, October 2006) Edition 3 plus all JavaScript 1.6 enhancements, plus Pythonic generators and array comprehensions ([a*a for (a in iter)]), block scope with let, destructuring assignment (var [a,b]=[1,2]) (New in JavaScript 1.7)
1.8 (Gecko 1.9, Firefox 3, June 2008) Edition 3 plus all JavaScript 1.7 enhancements, plus expression closures (function(x) x * x), generator expressions, and more (New in JavaScript 1.8)
JScript .NET (ASP.NET; no IE release) (JScript .NET is said to have been designed with the participation of other Ecma members)[45]

Conformance tests

In 2010, Ecma International started developing a standards test for Ecma 262 ECMAScript.[46] Test262 is an ECMAScript conformance test suite that can be used to check how closely a JavaScript implementation follows the ECMAScript 5th Edition Specification. The test suite contains thousands of individual tests, each of which tests some specific requirements of the ECMAScript specification.

Development of test262 is a project of Ecma Technical Committee 39 (TC39). The testing framework and individual tests are created by member organizations of TC39 and contributed to Ecma for use in Test262.

Important contributions were made by Google (Sputnik testsuite) and Microsoft who both contributed thousands of tests. The Test262 testsuite already contains more than 11,000 tests and is being developed further as of 2013.

The following table shows current conformance results of browser products. Lower scores are better, although scores can not be compared, as tests are not weighted. Also, be aware that Test262 itself is likely to contain bugs that may impact a browser's score. So browsers with a score significantly lower than the current test suite bug count may not necessarily do better than those with a higher one.[47] That may be particularly true when several browsers have a higher score in their current development builds as compared to their last released version.

Results of test262 (suite version: ES5, suite date: 2014-09-18)
Product Latest Stable Test262 failed Preview/Beta Test262 failed Alpha Test262 failed Nightly Test262 failed
Google Chrome 46.0.2490.86 m 207/11552 47.0.2526.69 beta-m 208/11552 48.0.2564.10 dev-m 203/11552 48.0.2569.0 canary 203/11552
Mozilla Firefox 42.0 260/11552 43.0 Beta 5 260/11552 44.0a2 (20151120004044) 260/11552 45.0a1 (20151120030227) 260/11552
ESR 38.4.0 228/11552
Internet Explorer 11.0.25 (11.0.9600.18097) 8/11552
Maxthon 18/11552
Opera 33.0.1990.115 207/11552 beta 34.0.2036.3 208/11552 developer 35.0.2052.0 210/11552
12.17 (classic) 11/11552
Safari 7.1 (9537.85) 7/11552

See also


  1. Stefanov, Stoyan (2010). JavaScript Patterns. O'Reilly Media, Inc. p. 5. ISBN 9781449396947. Retrieved 2016-01-12. The core JavaScript programming language [...] is based on the ECMAScript standard, or ES for short.
  2. "TC39 - ECMAScript® (formerly TC39-TG1)". Ecma International. Retrieved 22 August 2015.
  3. Krill, Paul (2008-06-23). "JavaScript creator ponders past, future". InfoWorld. Retrieved 2013-10-31.
  4. "Netscape and Sun Announce JavaScript, the Open, Cross-platform Object Scripting Language for Enterprise Networks and the Internet". Netscape. December 4, 1995. Archived from the original on 2007-09-16. Retrieved 2013-10-31.
  5. "Brendan's Roadmap Updates: Popularity". Archived from the original on 17 May 2008.
  6. "Industry Leaders to Advance Standardization of Netscape's JavaScript at Standards Body Meeting". Netscape. November 15, 1996. Archived from the original on 1998-12-03. Retrieved 2013-10-31.
  7. "Will there be a suggested file suffix for es4?". 2006-10-03. Retrieved 2013-10-31.
  8. "JScript VS JavaScript". 2015-11-25.
  9. 1 2 . EMCAScript. Retrieved on 2016-06-20.
  10. "Changes to JavaScript, Part 1: EcmaScript 5". YouTube. 2009-05-18. Retrieved 2013-10-31.
  11. 1 2 3 "ECMAScript 2015 Language Specification" (PDF). Ecma International. June 2015.
  12. 1 2 "ECMAScript 2016 Language Specification". Ecma International. June 2016.
  13. "strawman:strawman [ES Wiki]". 2013-09-18. Retrieved 2013-10-31.
  14. "tc39/ecma262". TC39. GitHub. Retrieved 27 December 2015.
  15. 2015-03-24 Meeting Notes. ESDiscuss. Also see Ecma withdrawn Standards. ECMA.
  16. "ES4 overview paper released". Retrieved 2013-10-31.
  17. "Proposed ECMAScript 4th Edition – Language Overview" (PDF). 23 October 2007.
  18. John Resig. "John Resig – Bug Fixes in JavaScript 2". Retrieved 2013-10-31.
  19. "Compatibility Between ES3 and Proposed ES4" (PDF). Retrieved 2013-10-31.
  21. "ECMAScript 3 and Beyond – IEBlog – Site Home – MSDN Blogs". 2007-10-30. Retrieved 2013-10-31.
  22. "What I think about ES4. - Albatross! - Site Home – MSDN Blogs". 2007-10-31. Retrieved 2013-10-31.
  23. "Open letter to Chris Wilson". Brendan Eich. 2007-10-31. Retrieved 2013-10-31.
  24. "JavaScript 2 and the Open Web". 2007-11-20. Retrieved 2014-01-20.
  25. "ECMAScript Harmony". Retrieved 2013-10-31.
  26. "A Major Milestone in JavaScript Standardization – JScript Blog – Site Home – MSDN Blogs". 2009-04-09. Retrieved 2013-10-31.
  27. "Ecma International finalises major revision of ECMAScript". Ecma International. 2009-04-09. Retrieved 2009-05-22.
  28. "Ecma latest news". Retrieved 2013-10-31.
  35. "About". ECMAScript. Retrieved 2009-12-17.
  36. "Server-side Javascript for Developers". 1 January 2015. Retrieved 9 August 2016.
  37. Keith Miller (July 11, 2016). "ES6 Feature Complete". WebKit.
  38. "Samsung/jerryscript". GitHub. Retrieved 2016-11-24.
  39. "Nashorn extensions". OpenJDK Wiki. Retrieved 2016-11-24.
  40. "Ejscript Overview". Embedthis Software. Retrieved 2016-11-14.
  41. Darrick Brown (May 25, 2006). "AS3 language 101 for C/C++ coders". Adobe Blogs: The Kiwi Project.
  42. "Caja Introduction". Google Developers. February 28, 2012.
  43. tedster (March 12, 2002). "JavaScript – JScript – ECMAScript version history". Retrieved 2009-12-17.
  44. "Version Information (JScript)". Archived from the original on 2009-12-17. Retrieved 2009-12-17.
  45. Andrew Clinick (July 14, 2000). "Introducing JScript .NET". Retrieved 2010-01-12.
  46. "ECMAScript Language – test262". Retrieved 2013-10-31.
  47. Schuster, Tom. "Bug 1453". bug database. Retrieved 12 October 2014.

External links

ISO Standard
Ecma Standards

This article is issued from Wikipedia - version of the 11/27/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.