- The Evolution Of The Conflict And Browser Incompatibility
- Submission To ECMA For Standardization
- What’s Next?
Many years ago, back in 1995, there was a browser called Netscape Navigator (sounds like a story already;). The internet connectivity was rather very slow as people used to use dial-up connections using telephone lines and modems. So when you were supposed to fill a form on a website, which was usually coded using a language like Perl, the validation of the input fields of any form required a full round trip to the server.
Brendan Eich (then a developer at Netscape Navigator) was assigned a task of developing this new scripting language which was then named Mocha. This was intended to be released as a part of Netscape Navigator 2. Mocha was later renamed to LiveScript before the release of Netscape Navigator 2. Netscape Communications then entered into an alliance with Sun Microsystems which was then really pushing hard for promoting Java.
The Evolution Of The Conflict And Browser Incompatibility
Submission To ECMA For Standardization
- The Core - This is based on ECMAScript. So the ECMAScript defines the syntax, data types, statements, operators, etc.
- Document Object Model (DOM) - This is what the browser renders as a hierarchy of nodes to be displayed to the client or the user.
- Browser Object Model (BOM) - This is what allows the developers to manipulate the browser window. Using the BOM the developers can access the browser features and manipulate them outside the context of the DOM or the page that is being rendered.
You can watch this space for the next article or you can subscribe to my Newsletter and I would notify you as soon as the next article is published. Don’t forget to leave a like or share the article if it was helpful!