Javascript, shouldn’t be confused with Java (programming language). It is a scripting language based on prototypes as some users might already know.
In the early years there were several issues with it including security issues and a lack of critical development tools such as Integrated development environments and debugers. There was no way to track error messages. It was magnified far beyond the initial purpose of its designers, yet knotted to incompatible browser object models, Javascript like Perl, suffered its initial years in the hands of sophisticated yet critical Java programmers and otherwise ignorant web designers. It was ended up into a junk without any consideration for future code use and compatibility.
Even though it is recognized as the most popular language on the web. It has now been widely recognized as the foundation of the next generation user friendly or client-side dynamic web applications. Yet not a lot of programmers view Javascript as an essential part of their day-to-day programming toolbox. In this context we have to look at the brief history of Javascript, its origin and development throughout these years.
Javascript was posthulated in 1995 in the need to leverage Netscape Navigator’s newly added support for Java applets more amicable to non-Java programmers and web developers. At the nascent stage Javascript was a programming language, written by Brendan Erich. It was used to be embedded in web pages. It was made to process numbers and access the contents of web forms. In the line of development, Javascript came to be known as Mocha then LiveWire then LiveScript. The core scripting syntax closely took after Java, so it was named JavaScript in the time of release. It was a powerful though simple scripting language.
Microsoft’s response to Javascript was another stimulating part in the development and growth of the language. As soon as Javascript started to become popular Microsoft counter-released VBScript language although capable of running onto windows platform only. On July 16,1996 they also released a part of JavaScript as “JScript”. An mesmerizing accomplishment was made to support new W3C-sanctioned standards like Cascading Stylesheets in Navigator’s JavaScript, which was one step ahead of IE 3.0, untill it showed up in the next released version 3.02.
The next development came with the hand of European Computer Manufacturers Association(ECMA) with an attempt to standardize the language as it fell unfortunate in the dearth of support for the document.images array in the IE3. Netscape and Sun joined their hands with ECMA make up this loophole and standardize the language. And it brought forth a new strange and incompatible object models: ECMAScript. In the meantime of standardization of JavaScript, Microsoft and Netscape launched the generation 4 browsers in the market. These newly designed browsers had their own proprietary document object models. With the birth of ‘Dynamic HTML’ the repression of JavaScript’s good heart took hold.
The next gen browser wars started raging. Top entrants started to feel the needful to develop a truly universal Document Object Model(DOM) with the W3C. This effort was recognized as Level 0 DOM or DOM level 0. Step on to this Century.
Now the question is : How far have we come?
JavaScript is enough flexible to overcome many of its weaknesses, but not enough to overcome radical, context-oriented object model incompatibilities.
JavaScript is now widely being used by companies such as KnowNow,Blox and more as client-side JavaScript to deliver the next generation web based apps.
Even Microsoft, with all its shout outs with C#, seems to admit the virility of JavaScript. One could simply come by a MSDN application or a single script, which is partly written in JavaScript.
Java has pretty much suffered in the hands of almost everyone including SUn and other major Software Corporations. Yet it has stood out of its ground. And conquered the web.
JavaScript History - from form validation to servers
JavaScript History: How Far We’ve Come
Javascript & jQuery Development
Javascript, shouldn’t be confused with Java (programming language). It is a scripting language based on prototypes as some users might already know.
In the early years there were several issues with it including security issues and a lack of critical development tools such as Integrated development environments and debugers. There was no way to track error messages. It was magnified far beyond the initial purpose of its designers, yet knotted to incompatible browser object models, Javascript like Perl, suffered its initial years in the hands of sophisticated yet critical Java programmers and otherwise ignorant web designers. It was ended up into a junk without any consideration for future code use and compatibility.
Even though it is recognized as the most popular language on the web. It has now been widely recognized as the foundation of the next generation user friendly or client-side dynamic web applications. Yet not a lot of programmers view Javascript as an essential part of their day-to-day programming toolbox. In this context we have to look at the brief history of Javascript, its origin and development throughout these years.
Javascript was posthulated in 1995 in the need to leverage Netscape Navigator’s newly added support for Java applets more amicable to non-Java programmers and web developers. At the nascent stage Javascript was a programming language, written by Brendan Erich. It was used to be embedded in web pages. It was made to process numbers and access the contents of web forms. In the line of development, Javascript came to be known as Mocha then LiveWire then LiveScript. The core scripting syntax closely took after Java, so it was named JavaScript in the time of release. It was a powerful though simple scripting language.
Microsoft’s response to Javascript was another stimulating part in the development and growth of the language. As soon as Javascript started to become popular Microsoft counter-released VBScript language although capable of running onto windows platform only. On July 16,1996 they also released a part of JavaScript as “JScript”. An mesmerizing accomplishment was made to support new W3C-sanctioned standards like Cascading Stylesheets in Navigator’s JavaScript, which was one step ahead of IE 3.0, untill it showed up in the next released version 3.02.
The next development came with the hand of European Computer Manufacturers Association(ECMA) with an attempt to standardize the language as it fell unfortunate in the dearth of support for the document.images array in the IE3. Netscape and Sun joined their hands with ECMA make up this loophole and standardize the language. And it brought forth a new strange and incompatible object models: ECMAScript. In the meantime of standardization of JavaScript, Microsoft and Netscape launched the generation 4 browsers in the market. These newly designed browsers had their own proprietary document object models. With the birth of ‘Dynamic HTML’ the repression of JavaScript’s good heart took hold.
The next gen browser wars started raging. Top entrants started to feel the needful to develop a truly universal Document Object Model(DOM) with the W3C. This effort was recognized as Level 0 DOM or DOM level 0. Step on to this Century.
Now the question is : How far have we come?
JavaScript is enough flexible to overcome many of its weaknesses, but not enough to overcome radical, context-oriented object model incompatibilities.
JavaScript is now widely being used by companies such as KnowNow,Blox and more as client-side JavaScript to deliver the next generation web based apps.
Even Microsoft, with all its shout outs with C#, seems to admit the virility of JavaScript. One could simply come by a MSDN application or a single script, which is partly written in JavaScript.
Java has pretty much suffered in the hands of almost everyone including SUn and other major Software Corporations. Yet it has stood out of its ground. And conquered the web.
About Gunner Technology
View all posts by Gunner Technology →