The scope of the ECMAScript 4 changes caused a rift to form in TC-39, with some members feeling that the fourth edition was trying to accomplish too much.
A group of leaders from Yahoo, Google, and Microsoft created an alternate proposal for the next version of ECMAScript that they initially called ECMAScript 3.1.
The “3.1” was intended to show that this was an incremental change to the existing standard.
Double your dating first ebook
The Java Script core language features are defined in a standard called ECMA-262.
The language defined in this standard is called ECMAScript.
What you know as Java Script in browsers and is actually a superset of ECMAScript.
Browsers and add more functionality through additional objects and methods, but the core of the language remains as defined in ECMAScript.
The ongoing development of ECMA-262 is vital to the success of Java Script as a whole, and this book covers the changes brought about by the most recent major update to the language: ECMAScript 6. The popularity of Ajax was ushering in a new age of dynamic web applications, while Java Script hadn’t changed since the third edition of ECMA-262 was published in 1999.
TC-39, the committee responsible for driving the ECMAScript development process, put together a large draft specification for ECMAScript 4.
ECMAScript 4 was massive in scope, introducing changes both small and large to the language.
Updated features included new syntax, modules, classes, classical inheritance, private object members, optional type annotations, and more.
Although there was an early attempt to reconcile ECMAScript 3.1 and ECMAScript 4, this ultimately failed as the two camps had difficulty with the very different perspectives on how the language should grow.
In 2008, Brendan Eich, the creator of Java Script, announced that TC-39 would focus its efforts on standardizing ECMAScript 3.1.
They would table the major syntax and feature changes of ECMAScript 4 until after the next version of ECMAScript was standardized, and all members of the committee would work to bring the best pieces of ECMAScript 3.1 and 4 together after that point into an effort initially nicknamed ECMAScript Harmony.