Why was ECMAScript 4th edition completely scrapped?

Question

I\'ve been looking for some information regarding the scrapped ECMAScript 4th Edition without much success, even on SO. I know Mozilla\'s JavaScript 1.7 implemented many (a

Answer 1

Basically it was becoming a kitchen sink with too many features to be implemented.

Answer 2

If you have a spare 55 minutes for the subject, see the video Douglas Crockford: “The State and Future of ECMAScript” or the transcript.

Answer 3

There was some discussion of the in the interviews of Coders At Work, two of the interviewees were on opposite sides of this issue.

It appears to have come down to fundamental disagreement about what the language should contain between those working on v4 and some other well respected members of the community.

(I highly recommend this book by the way)

Answer 4

Simply put, there was no ECMAScript 4th Edition. From the 5th edition specification:

Significant work was done to develop a fourth edition of ECMAScript. Although that work was not completed and not published as the fourth edition of ECMAScript, it informs continuing evolution of the language. The present fifth edition of ECMAScript (published as ECMA-262 5th edition) codifies de facto interpretations of the language specification that have become common among browser implementations and adds support for new features that have emerged since the publication of the third edition.

Basically, there were a lot of very strong opinions about how to move JavaScript forward, many of which were incompatible, some of which had mostly been assembled into what some thought would be the 4th edition before things fell apart (not least because of lack of support from some important implementors). Meanwhile, a new edition of the standard was very, very overdue, and so after a lot of advance negotiation, the various parties got together in Oslo in July 2008 and agreed a way forward (Brendan Eich [inventor of JavaScript] later termed that approach "Harmony" when writing it up).

Harmony deferred some things, put some things completely off the table forever (namespaces, packages, early binding), and — importantly — allowed the committee to move forward with the first specification update since 1999: The 5th edition.