A brief historical review of
JavaScript implementation
1. Brief historical review
- Cause:The need for a large number of round trips with the server to validate simple forms has become a pain point for users.
With the increasing popularity of the Web, the demand for client-side simplified language is becoming stronger. At that time, most users used the 28.8kbit/s mandatory demodulator to surf the Internet, making web pages larger and more complex. The need for a large number of round trips with the server to validate simple forms has become a pain point for users. Netscape was a leading technology innovation company at the time, and it put the development of a client-side scripting language to handle this simple data verification on the agenda. - In 1995, a Netscape engineer named Brendan Eich began to develop a scripting language called Mocha (later renamed LiveScript ) for the upcoming Netscape Navigator 2 . The plan at the time was to use it on both the client and server side. It was called LiveWire on the server side.
- In order to catch up with the release time, Netscape and Sun have formed a development alliance to jointly complete the development of LiveScript. Just before the official release of Netscape Navigator 2, Netscape renamed LiveScript to JavaScript in order to catch the ride of the media's enthusiastic hype about Java.
- Due to the success of JavaScript 1.0, Netscape released version 1.1 in Netscape Navigator 3. Soon after the release, Microsoft released IE3, which contains its own JavaScript implementation called JScript.
- Due to the emergence of Microsoft JavaScript, == means that there are two versions: JavaScript in Netscape Navigator and JScript in IE. ==Because JavaScript has no standard for its grammar or features, the coexistence of the two versions makes this problem more prominent. So far, JavaScript has embarked on the journey of standardization.
- In 1997, JavaScript 1.1 was submitted as a proposal to the European Computer Manufacturers Association (Ecma). Technical Committee 39 (TC39) has undertaken the task of "standardizing the syntax and semantics of a universal, cross-platform, vendor-neutral scripting language". It took several months to create ECMA-262, the new scripting language standard ECMAScript.
2. JavaScript implementation
Although what we usually call ECMAScript refers to JavaScript, JavaScript is far from limited to that defined by ECMA-262. The complete JavaScript implementation includes the following parts.
1. Core (ECMAScript)
2. Document Object Model (DOM)
3. Browser Object Model (BOM)
