We know nowadays javascript have great importance in programming. Early days it just used for basic validation purpose but now the complete application logic is implmented on the client side than the serverside.
Lets do a rewind, In the starting of 2000 time there is very less importance for the javascript language. Javascript just used only in the case of validation purpose. At that time javascript become programmers headache because it was not standardised. So the user needs to do different programming for different browsers. Due to this issue the javascript community decided to create a standardization
ECMA Standard
In November 1996 Netscape submitted a standard specification for ECMA script standardization and the first edition of the ECMA 262 standard released on June 1997 called ECMAScript 1 after the release of ECMAScript 1, ECMAScript 2 and 3 released by doing few more modification on ECMAScript 1.
The ECMAScript 4 which have huge upgrade to ES3 relased on early 2000. Microsoft’s JScript and Adobe’s ActionScript had implemented some of its features, but work stopped completely on the ES4 specification shortly after the interim report’s release. Around this time, a new technique for creating dynamic client-side web applications using JavaScript emerged, which brought about a sort of JavaScript renaissance. JavaScript toolkit libraries like jQuery, Prototype, Dojo and Mootools were all released during this period of JavaScript rebirth.
After the ECMAScript 4 release the developers team moves to two seprate camps. In one corner was the “ECMAScript 4 Camp,” composed of Adobe, Mozilla, Opera & Google, who still wanted to work towards the massive upgrade. In the other corner was Microsoft & Yahoo, the “ECMAScript 3.1 Camp”, seeking a small subset of ES4, which would be more of an incremental upgrade of ES3 containing some minor features and bug fixes.
ECMAScript 5, the incremental upgrade to ES3, was released in December 2009, more than a decade after ES3. It is the version of JavaScript that is fully supported in all the browsers in use today except for Internet Explorer 8, of course.
It added several enhancements to the standard library such as:
JSON parsing/serialization support
Array prototype methods (like map and forEach)
Methods for listing properties (like Object.keys).
There were also syntactic updates like:
Allowances for dangling commas at the end of lists or object definitions
Allowances for reserved words (like new or for) as object properties
Finally, it introduced strict mode, which made JavaScript a cleaner language by forbidding some features, performing additional runtime checks, and throwing more exceptions.
ECMAScript 6
ECMAScript 6 was originally planned to be released in 2013, but wasn’t officially released until in June 2015. ECMAScript Harmony was the codename for the group of features following ES5, but it became clear that its goals were still too ambitious, so TC39 decided to break it up into two phases:
The highest priority features would be in the next release of ECMAScript. It was codenamed ECMAScript.next in order to try to avoid the whole numbering fiasco with the lost ECMAScript 4.
The remaining features would find their way into the following version.
As ECMAScript.next matured, the code name was dropped and it began going by ECMAScript 6, or simply, ES6. However, in late 2014, TC39 decided to rename ECMAScript 6 to ECMAScript 2015 in light of the new plan to release ECMAScript on a yearly cadence. By this time the standard was already well-established as ECMAScript 6, so most people still know it as ES6 and refer to it as such.
ES6 features are slowly rolling into the interpreters of our modern browsers and servers. The ES6 compatibility table tracks just how much of the standard each engine supports
ECMAScript 7
Work on ECMAScript 7 has already begun and the current proposals are on GitHub. As mentioned earlier, TC39 is transitioning to a yearly release cadence, so the releases will now be more incremental. And since ECMAScript 7 officially kicks off the yearly release cycle it has also been renamed to ECMAScript 2016. I may preview some of its proposed features at the end of this series.
No comments:
Post a Comment