JavaScript

Unofficial logo from JSConf EU 2011
Paradigm(s)	Multi-paradigm: scripting, object-oriented (prototype-based), imperative, functional[1]
Appeared in	1995
Designed by	Brendan Eich
Developer	Netscape Communications Corporation, Mozilla Foundation
Stable release	1.8.5[2] (March 22, 2011; 14 months ago  (2011-03-22))
Typing discipline	dynamic, weak, duck
Major implementations	KJS, Rhino, SpiderMonkey, V8, WebKit, Carakan, Chakra
Influenced by	C, Java, Perl, Python, Scheme, Self
Influenced	ActionScript, CoffeeScript, Dart, JScript .NET, Objective-J, QML, TIScript
JavaScript at Wikibooks

JavaScript (sometimes abbreviated JS) is a prototype-based scripting language that is dynamic, weakly typed and has first-class functions. It is a multi-paradigm language, supporting object-oriented,^[5] imperative, and functional^[1][6] programming styles.

JavaScript was formalized in the ECMAScript language standard and is primarily used in the form of client-side JavaScript, implemented as part of a Web browser in order to provide enhanced user interfaces and dynamic websites. This enables programmatic access to computational objects within a host environment.

JavaScript's use in applications outside Web pages — for example in PDF documents, site-specific browsers, and desktop widgets — is also significant. Newer and faster JavaScript VMs and frameworks built upon them (notably Node.js) have also increased the popularity of JavaScript for server-side web applications.

JavaScript uses syntax influenced by that of C. JavaScript copies many names and naming conventions from Java, but the two languages are otherwise unrelated and have very different semantics. The key design principles within JavaScript are taken from the Self and Scheme programming languages.^[7]

History[link]

Birth at Netscape[link]

JavaScript was originally developed in Netscape, by Brendan Eich. Battling with Microsoft over the Internet, Netscape considered their client-server solution as a distributed OS, running a portable version of Sun Microsystem's Java. Because Java was a competitor of C++ and aimed at professional programmers, Netscape also wanted a lightweight interpreted language that would complement Java by appealing to nonprofessional programmers, like Microsoft's VB.^[9] (see JavaScript and Java)

Developed under the name Mocha, LiveScript was the official name for the language when it first shipped in beta releases of Netscape Navigator 2.0 in September 1995, but it was renamed JavaScript in a joint announcement with Sun Microsystems on December 4, 1995,^[10] when it was deployed in the Netscape browser version 2.0B3.^[11]

The change of name from LiveScript to JavaScript roughly coincided with Netscape adding support for Java technology in its Netscape Navigator web browser. The final choice of name caused confusion, giving the impression that the language was a spin-off of the Java programming language, and the choice has been characterized by many as a marketing ploy by Netscape to give JavaScript the cachet of what was then the hot new web programming language.^[12][13] It has also been claimed  that the language's name is the result of a co-marketing deal between Netscape and Sun, in exchange for Netscape bundling Sun's Java runtime with its then-dominant browser.

Server-side JavaScript[link]

Netscape introduced an implementation of the language for server-side scripting with Netscape Enterprise Server, first released in December, 1994 (soon after releasing JavaScript for browsers).^[14][15] Since the mid-2000s, there has been a proliferation of server-side JavaScript implementations, with node.js being merely one example.^[16][17]

Adoption by Microsoft[link]

JavaScript very quickly gained widespread success as a client-side scripting language for web pages. Microsoft introduced JavaScript support in its own web browser, Internet Explorer, in version 3.0, released in August 1996.^{[18][not in citation given]} Microsoft's webserver, Internet Information Server, introduced support for server-side scripting in JavaScript with release 3.0 (1996). Microsoft started to promote webpage scripting using the umbrella term Dynamic HTML.

Microsoft's JavaScript implementation was later renamed to JScript to avoid trademark issues. JScript added new date methods to fix the Y2K-problematic methods in JavaScript, which were based on Java's java.util.Date class.

Standardization[link]

In November 1996, Netscape announced that it had submitted JavaScript to Ecma International for consideration as an industry standard, and subsequent work resulted in the standardized version named ECMAScript.^[19]

Later developments[link]

JavaScript has become one of the most popular programming languages on the web. Initially, however, many professional programmers denigrated the language because its target audience was web authors and other such "amateurs", among other reasons.^[20] The advent of Ajax returned JavaScript to the spotlight and brought more professional programming attention. The result was a proliferation of comprehensive frameworks and libraries, improved JavaScript programming practices, and increased usage of JavaScript outside of web browsers, as seen by the proliferation of server-side JavaScript platforms.

In January 2009, the CommonJS project was founded with the goal of specifying a common standard library mainly for JavaScript development outside the browser.^[21]

Trademark[link]

Today, "JavaScript" is a trademark of Oracle Corporation.^[22] It is used under license for technology invented and implemented by Netscape Communications and current entities such as the Mozilla Foundation.^[23]

Features[link]

The following features are common to all conforming ECMAScript implementations, unless explicitly specified otherwise.

Imperative and structured[link]

JavaScript supports much of the structured programming syntax from C (e.g., if statements, while loops, switch statements, etc.). One partial exception is scoping: C-style block-level scoping is not supported (instead, JavaScript has function-level scoping). JavaScript 1.7, however, supports block-level scoping with the let keyword. Like C, JavaScript makes a distinction between expressions and statements. One syntactic difference from C is automatic semicolon insertion, in which the semicolons that terminate statements can be omitted.^[24]

Dynamic[link]

dynamic typing

As in most scripting languages, types are associated with values, not with variables. For example, a variable x could be bound to a number, then later rebound to a string. JavaScript supports various ways to test the type of an object, including duck typing.^[25]

object based

JavaScript is almost entirely object-based. JavaScript objects are associative arrays, augmented with prototypes (see below). Object property names are string keys: obj.x = 10 and obj['x'] = 10 are equivalent, the dot notation being syntactic sugar. Properties and their values can be added, changed, or deleted at run-time. Most properties of an object (and those on its prototype inheritance chain) can be enumerated using a for...in loop. JavaScript has a small number of built-in objects such as Function and Date.

run-time evaluation

JavaScript includes an eval function that can execute statements provided as strings at run-time.

Functional[link]

first-class functions

Functions are first-class; they are objects themselves. As such, they have properties and methods, such as length and call();^[26] and they can be assigned to variables, passed as arguments, returned by other functions, and manipulated like any other object.^[27] Any reference to a function allows it to be invoked using the () operator.^[28]

nested functions and closures

"Inner" or "nested" functions are functions defined within another function. They are created each time the outer function is invoked. In addition to that, each created function forms a lexical closure: the lexical scope of the outer function, including any constants, local variables and argument values, become part of the internal state of each inner function object, even after execution of the outer function concludes.^[29]

Prototype-based[link]

prototypes

JavaScript uses prototypes instead of classes for inheritance. It is possible to simulate many class-based features with prototypes in JavaScript.

functions as object constructors

Functions double as object constructors along with their typical role. Prefixing a function call with new creates a new object and calls that function with its local this keyword bound to that object for that invocation. The constructor's prototype property determines the object used for the new object's internal prototype. JavaScript's built-in constructors, such as Array, also have prototypes that can be modified.

functions as methods

Unlike many object-oriented languages, there is no distinction between a function definition and a method definition. Rather, the distinction occurs during function calling; a function can be called as a method. When a function is called as a method of an object, the function's local this keyword is bound to that object for that invocation.

Miscellaneous[link]

run-time environment

JavaScript typically relies on a run-time environment (e.g. in a web browser) to provide objects and methods by which scripts can interact with "the outside world". In fact, it relies on the environment to provide the ability to include/import scripts (e.g. HTML <script> elements). (This is not a language feature per se, but it is common in most JavaScript implementations.)

variadic functions

An indefinite number of parameters can be passed to a function. The function can access them through formal parameters and also through the local arguments object.

array and object literals

Like many scripting languages, arrays and objects (associative arrays in other languages) can each be created with a succinct shortcut syntax. In fact, these literals form the basis of the JSON data format.

regular expressions

JavaScript also supports regular expressions in a manner similar to Perl, which provide a concise and powerful syntax for text manipulation that is more sophisticated than the built-in string functions.

Vendor-specific extensions[link]

JavaScript is officially managed by Mozilla Foundation, and new language features are added periodically. However, only some non-Mozilla JavaScript engines support these new features:

• property getter and setter functions (also supported by WebKit, Opera,^[30] ActionScript, and Rhino)^[31]
• conditional catch clauses
• iterator protocol adopted from Python
• shallow generators-coroutines also adopted from Python
• array comprehensions and generator expressions also adopted from Python
• proper block scope via the let keyword
• array and object destructuring (limited form of pattern matching)
• concise function expressions (function(args) expr)
• ECMAScript for XML (E4X), an extension that adds native XML support to ECMAScript

Syntax and semantics[link]

As of 2011^[update], the latest version of the language is JavaScript 1.8.5. It is a superset of ECMAScript (ECMA-262) Edition 3. Extensions to the language, including partial ECMAScript for XML (E4X) (ECMA-357) support and experimental features considered for inclusion into future ECMAScript editions, are documented here.^[32]

Simple examples[link]

There is no built-in I/O functionality in JavaScript; the runtime environment provides that. In a web browser, here is the simplest "hello world" example: <syntaxhighlight lang="javascript"> alert("Hello world!"); </syntaxhighlight>

A simple recursive function: <syntaxhighlight lang="javascript"> function factorial(n) {

   if (n === 0) {
       return 1;
   }
   return n * factorial(n - 1);

} </syntaxhighlight>

Anonymous function (or lambda) syntax and closure example: <syntaxhighlight lang="javascript"> function displayClosure() {

   var count = 0;
   return function () {
       return ++count;
   };

} var inc = displayClosure(); inc(); // returns 1 inc(); // returns 2 inc(); // returns 3 </syntaxhighlight>

Variadic function demonstration (arguments is a special variable). <syntaxhighlight lang="javascript"> function sum() {

   var i, x = 0;
   for (i = 0; i < arguments.length; ++i) {
       x += arguments[i];
   }
   return x;

} sum(1, 2, 3); // returns 6 </syntaxhighlight>

More advanced example[link]

This sample code showcases various JavaScript features.

   var checkInt = function (x) { // inner function
       if (x % 1 !== 0) {
           throw new TypeError(x + " is not an integer"); // throw an exception
       }
       return x;
   };
   this.a = checkInt(x);
   // ^ semicolons are optional
   this.b = checkInt(y);

   constructor: LCMCalculator, // when reassigning a prototype, set the constructor property appropriately
   gcd: function () { // method that calculates the greatest common divisor
       // Euclidean algorithm:
       var a = Math.abs(this.a), b = Math.abs(this.b), t;
       if (a < b) {
           // swap variables
           t = b;
           b = a;
           a = t;
       }
       while (b !== 0) {
           t = b;
           b = a % b;
           a = t;
       }
       // Only need to calculate GCD once, so "redefine" this method.
       // (Actually not redefinition - it's defined on the instance itself,
       // so that this.gcd refers to this "redefinition" instead of LCMCalculator.prototype.gcd.)
       // Also, 'gcd' === "gcd", this['gcd'] === this.gcd
       this['gcd'] = function () {
           return a;
       };
       return a;
   },
   // Object property names can be specified by strings delimited by double (") or single (') quotes.
   "lcm" : function () {
       // Variable names don't collide with object properties, e.g. |lcm| is not |this.lcm|.
       // not using |this.a * this.b| to avoid FP precision issues
       var lcm = this.a / this.gcd() * this.b;
       // Only need to calculate lcm once, so "redefine" this method.
       this.lcm = function () {
           return lcm;
       };
       return lcm;
   },
   toString: function () {
       return "LCMCalculator: a = " + this.a + ", b = " + this.b;
   }

   document.write(x + "
");

   return new LCMCalculator(pair[0], pair[1]);

   return a.lcm() - b.lcm();

   output(obj + ", gcd = " + obj.gcd() + ", lcm = " + obj.lcm());

The following output should be displayed in the browser window.

Use in web pages[link]

The most common use of JavaScript is to write functions that are embedded in or included from HTML pages and that interact with the Document Object Model (DOM) of the page. Some simple examples of this usage are:

• Loading new page content or submitting data to the server via AJAX without reloading the page (for example, a social network might allow the user to post status updates without leaving the page)
• Animation of page elements, fading them in and out, resizing them, moving them, etc.
• Interactive content, for example games, and playing audio and video
• Validating input values of a web form to make sure that they are acceptable before being submitted to the server.
• Transmitting information about the user's reading habits and browsing activities to various websites. Web pages frequently do this for web analytics, ad tracking, personalization or other purposes.^[33]

Because JavaScript code can run locally in a user's browser (rather than on a remote server), the browser can respond to user actions quickly, making an application more responsive. Furthermore, JavaScript code can detect user actions which HTML alone cannot, such as individual keystrokes. Applications such as Gmail take advantage of this: much of the user-interface logic is written in JavaScript, and JavaScript dispatches requests for information (such as the content of an e-mail message) to the server. The wider trend of Ajax programming similarly exploits this strength.

A JavaScript engine (also known as JavaScript interpreter or JavaScript implementation) is an interpreter that interprets JavaScript source code and executes the script accordingly. The first JavaScript engine was created by Brendan Eich at Netscape Communications Corporation, for the Netscape Navigator web browser. The engine, code-named SpiderMonkey, is implemented in C. It has since been updated (in JavaScript 1.5) to conform to ECMA-262 Edition 3. The Rhino engine, created primarily by Norris Boyd (formerly of Netscape; now at Google) is a JavaScript implementation in Java. Rhino, like SpiderMonkey, is ECMA-262 Edition 3 compliant.

A web browser is by far the most common host environment for JavaScript. Web browsers typically use the public API to create "host objects" responsible for reflecting the Document Object Model (DOM) into JavaScript. The web server is another common application of the engine. A JavaScript webserver would expose host objects representing an HTTP request and response objects, which a JavaScript program could then manipulate to dynamically generate web pages.

Because JavaScript is the only language that the most popular browsers share support for, it has become a target language for many frameworks in other languages, even though JavaScript was never intended to be such a language.^[34] Despite the performance limitations inherent to its dynamic nature, the increasing speed of JavaScript engines has made the language a surprisingly feasible compilation target.

Example script[link]

Below is a minimal example of a standards-conforming web page containing JavaScript (using HTML 4.01 syntax) and the DOM: <syntaxhighlight lang="html4strict"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html>

 <head><title>simple page</title></head>
 <body>

This is JavaScript

   <script type="text/javascript">
     document.write('Hello World!');

var h1 = document.getElementById("header"); // holds a reference to the

tag h1 = document.getElementsByTagName("h1")[0]; // accessing the same

element </script> <noscript> Your browser either does not support JavaScript, or has JavaScript turned off. </noscript> </body> </html> </syntaxhighlight>

Compatibility considerations[link]

Because JavaScript runs in widely varying environments, an important part of testing and debugging is to test and verify that the JavaScript works across multiple browsers.

The DOM interfaces for manipulating web pages are not part of the ECMAScript standard, or of JavaScript itself. Officially, the DOM interfaces are defined by a separate standardization effort by the W3C; in practice, browser implementations differ from the standards and from each other, and not all browsers execute JavaScript.

To deal with these differences, JavaScript authors can attempt to write standards-compliant code which will also be executed correctly by most browsers; failing that, they can write code that checks for the presence of certain browser features and behaves differently if they are not available.^[35] In some cases, two browsers may both implement a feature but with different behavior, and authors may find it practical to detect what browser is running and change their script's behavior to match.^[36][37] Programmers may also use libraries or toolkits which take browser differences into account.

Furthermore, scripts may not work for some users. For example, a user may:

• use an old or rare browser with incomplete or unusual DOM support,
• use a PDA or mobile phone browser which cannot execute JavaScript,
• have JavaScript execution disabled as a security precaution,
• use a speech browser due to, for example, a visual disability.

To support these users, web authors can try to create pages which degrade gracefully on user agents (browsers) which do not support the page's JavaScript. In particular, the page should remain usable albeit without the extra features that the JavaScript would have added. An alternative approach that many find preferable is to first author content using basic technologies that work in all browsers, then enhance the content for users that have JavaScript enabled. This is known as progressive enhancement.

Accessibility[link]

Assuming that the user has not disabled its execution, client-side web JavaScript should be written to enhance the experiences of visitors with visual or physical disabilities, and certainly should avoid denying information to these visitors.^[38]

Screen readers, used by the blind and partially sighted, can be JavaScript-aware and so may access and read the page DOM after the script has altered it. The HTML should be as concise, navigable and semantically rich as possible whether the scripts have run or not. JavaScript should not be totally reliant on mouse-specific events so as to deny its benefits to users who either cannot use a mouse or who choose to favor the keyboard for whatever reason. Equally, although hyperlinks and webforms can be navigated and operated from the keyboard, accessible JavaScript should not require keyboard events either. There are device-independent events such as onfocus and onchange that are preferable in most cases.^[38]

JavaScript should not be used in a way that is confusing or disorienting to any web user. For example, using script to alter or disable the normal functionality of the browser, such as by changing the way the back-button or the refresh event work, is usually best avoided. Equally, triggering events that the user may not be aware of reduces the user's sense of control as do unexpected scripted changes to the page content.^[39]

Often the process of making a complex web page as accessible as possible becomes a nontrivial problem where issues become matters of debate and opinion, and where compromises are necessary in the end. However, user agents and assistive technologies are constantly evolving and new guidelines and relevant information are continually being published on the web.^[38]

Security[link]

JavaScript and the DOM provide the potential for malicious authors to deliver scripts to run on a client computer via the web. Browser authors contain this risk using two restrictions. First, scripts run in a sandbox in which they can only perform web-related actions, not general-purpose programming tasks like creating files. Second, scripts are constrained by the same origin policy: scripts from one web site do not have access to information such as usernames, passwords, or cookies sent to another site. Most JavaScript-related security bugs are breaches of either the same origin policy or the sandbox.

Cross-site vulnerabilities[link]

A common JavaScript-related security problem is cross-site scripting, or XSS, a violation of the same-origin policy. XSS vulnerabilities occur when an attacker is able to cause a target web site, such as an online banking website, to include a malicious script in the webpage presented to a victim. The script in this example can then access the banking application with the privileges of the victim, potentially disclosing secret information or transferring money without the victim's authorization. A solution to XSS vulnerabilities is to use HTML escaping whenever displaying untrusted data.

Some browsers include partial protection against reflected XSS attacks, in which the attacker provides a URL including malicious script. However, even users of those browsers are vulnerable to other XSS attacks, such as those where the malicious code is stored in a database. Only correct design of Web applications on the server side can fully prevent XSS.

XSS vulnerabilities can also occur because of implementation mistakes by browser authors.^[40]

Another cross-site vulnerability is cross-site request forgery or CSRF. In CSRF, code on an attacker's site tricks the victim's browser into taking actions the user didn't intend at a target site (like transferring money at a bank). It works because, if the target site relies only on cookies to authenticate requests, then requests initiated by code on the attacker's site will carry the same legitimate login credentials as requests initiated by the user. In general, the solution to CSRF is to require an authentication value in a hidden form field, and not only in the cookies, to authenticate any request that might have lasting effects. Checking the HTTP Referrer header can also help.

"JavaScript hijacking" is a type of CSRF attack in which a <script> tag on an attacker's site exploits a page on the victim's site that returns private information such as JSON or JavaScript. Possible solutions include:

• requiring an authentication token in the POST and GET parameters for any response that returns private information
• using POST and never GET for requests that return private information

Misplaced trust in the client[link]

Developers of client-server applications must recognize that untrusted clients may be under the control of attackers. Thus any secret embedded in JavaScript could be extracted by a determined adversary, and the application author cannot assume that his JavaScript runs as intended, or at all. Some implications:

• Web site authors cannot perfectly conceal how their JavaScript operates, because the code is sent to the client, and obfuscated code can be reverse-engineered.
• JavaScript form validation only provides convenience for users, not security. If a site verifies that the user agreed to its terms of service, or filters invalid characters out of fields that should only contain numbers, it must do so on the server, not only the client.
• Scripts can be selectively disabled, so JavaScript can't be relied on to prevent operations such as "save image".^[41]
• It is extremely bad practice to embed sensitive information such as passwords in JavaScript because it can be extracted by an attacker.

Browser and plugin coding errors[link]

JavaScript provides an interface to a wide range of browser capabilities, some of which may have flaws such as buffer overflows. These flaws can allow attackers to write scripts which would run any code they wish on the user's system.

These flaws have affected major browsers including Firefox,^[42] Internet Explorer,^[43] and Safari.^[44]

Plugins, such as video players, Adobe Flash, and the wide range of ActiveX controls enabled by default in Microsoft Internet Explorer, may also have flaws exploitable via JavaScript, and such flaws have been exploited in the past.^[45][46]

In Windows Vista, Microsoft has attempted to contain the risks of bugs such as buffer overflows by running the Internet Explorer process with limited privileges.^[47] Google Chrome similarly limits page renderers in its own "sandbox".

Sandbox implementation errors[link]

Web browsers are capable of running JavaScript outside of the sandbox, with the privileges necessary to, for example, create or delete files. Of course, such privileges aren't meant to be granted to code from the web.

Incorrectly granting privileges to JavaScript from the web has played a role in vulnerabilities in both Internet Explorer^[48] and Firefox.^[49] In Windows XP Service Pack 2, Microsoft demoted JScript's privileges in Internet Explorer.^[50]

Microsoft Windows allows JavaScript source files on a computer's hard drive to be launched as general-purpose, non-sandboxed programs. This makes JavaScript (like VBScript) a theoretically viable vector for a Trojan horse, although JavaScript Trojan horses are uncommon in practice.^[51] (See Windows Script Host.)

Uses outside web pages[link]

In addition to web browsers and servers, JavaScript interpreters are embedded in a number of tools. Each of these applications provides its own object model which provides access to the host environment, with the core JavaScript language remaining mostly the same in each application.

Embedded scripting language[link]

• Google's Chrome extensions, Opera's extensions, Apple's Safari 5 extensions, Apple's Dashboard Widgets, Microsoft's Gadgets, Yahoo! Widgets, Google Desktop Gadgets, and Serence Klipfolio are implemented using JavaScript.
• Adobe's Acrobat and Adobe Reader support JavaScript in PDF files.^[52]
• Tools in the Adobe Creative Suite, including Photoshop, Illustrator, Dreamweaver, and InDesign, allow scripting through JavaScript.
• OpenOffice.org office application suite allows for JavaScript as one of its scripting languages.
• The interactive music signal processing software Max/MSP released by Cycling '74, offers a JavaScript model of its environment for use by developers. It allows much more precise control than the default GUI-centric programming model.
• ECMAScript was included in the VRML97 standard for scripting nodes of VRML scene description files.
• Some high-end Philips universal remote panels, including TSU9600 and TSU9400, can be scripted using a JavaScript-based tool called ProntoScript.^[53]
• Sphere is an open source and cross platform computer program designed primarily to make role-playing games that use JavaScript as a scripting language.
• The open-source Re-Animator framework allows developing 2D sprite-based games using JavaScript and XML.
• Methabot is a web crawler that uses JavaScript as scripting language for custom filetype parsers and data extraction using E4X.
• The Unity game engine supports a modified JavaScript for scripting (in addition to C# and Boo) via Mono.^[54]
• DX Studio (3D engine) uses the SpiderMonkey implementation of JavaScript for game and simulation logic.^[55]
• Maxwell Render (rendering software) provides an ECMA standard based scripting engine for tasks automation.^[56]
• Google Apps Script in Google Spreadsheets and Google Sites allows users to create custom formulas, automate repetitive tasks and also interact with other Google products such as Gmail.^[57]
• Many IRC clients, like ChatZilla or XChat, use JavaScript for their scripting abilities.^[58][59]

Scripting engine[link]

• Microsoft's Active Scripting technology supports JScript as a scripting language.^[60]
• The Java programming language, in version SE 6 (JDK 1.6), introduced the javax.script package, including a JavaScript implementation based on Mozilla Rhino. Thus, Java applications can host scripts that access the application's variables and objects, much like web browsers host scripts that access the browser's Document Object Model (DOM) for a webpage.^[61][62]
• The Qt C++ toolkit includes a QtScript module to interpret JavaScript, analogous to Java's javax.script package.^[63]
• JSDB (JavaScript for Databases) is an open-source JavaScript shell for Windows, Mac OS X, Linux, and Unix, which extends the Mozilla JavaScript engine with file, database, email, and network objects.
• jslibs is an open-source JavaScript shell for Windows and Linux which extends the Mozilla JavaScript engine. It has the ability to call functions in commonly used libraries like NSPR, SQLite, libTomCrypt, OpenGL, OpenAL, and librsvg.
• Late Night Software's JavaScript OSA (aka JavaScript for OSA, or JSOSA) is a freeware alternative to AppleScript for Mac OS X. It is based on the Mozilla 1.5 JavaScript implementation, with the addition of a MacOS object for interaction with the operating system and third-party applications.^[64]

Application platform[link]

• ActionScript, the programming language used in Adobe Flash, is another implementation of the ECMAScript standard.
• The Mozilla platform, which underlies Firefox, Thunderbird, and some other web browsers, uses JavaScript to implement the graphical user interface (GUI) of its various products.
• Adobe Integrated Runtime is a JavaScript runtime that allows developers to create desktop applications.
• myNFC.org is a JavaScript based framework that allows developers to create applications for smart phones.
• webOS uses the WebKit implementation of JavaScript in its SDK to allow developers to create stand-alone applications solely in JavaScript.
• CA, Inc.'s AutoShell cross-application scripting environment is built on JavaScript/SpiderMonkey with preprocessor like extensions for command definitions and custom classes for various system related tasks like file i/o, operation system command invocation and redirection and COM scripting.
• GNOME Shell, the shell for the GNOME 3 desktop environment.^[65] The Seed,^[66] Gjs (from Gnome), and Kjsembed^[67] (from KDE) packages are aimed to utilize these^{[clarification needed]} needs. ^[68][69]
• Qt Quick's markup language (QML) is using JavaScript for the application logic, and the declarative syntax is JavaScript-like. QML has been available since Qt 4.7.

Development tools[link]

Within JavaScript, access to a debugger becomes invaluable when developing large, non-trivial programs. Because there can be implementation differences between the various browsers (particularly within the Document Object Model), it is useful to have access to a debugger for each of the browsers that a web application targets.^[70]

Script debuggers are available for Internet Explorer, Firefox, Safari, Google Chrome, and Opera.^[71]

Three debuggers are available for Internet Explorer: Microsoft Visual Studio is the richest of the three, closely followed by Microsoft Script Editor (a component of Microsoft Office),^[72] and finally the free Microsoft Script Debugger which is far more basic than the other two. The free Microsoft Visual Web Developer Express provides a limited version of the JavaScript debugging functionality in Microsoft Visual Studio. Internet Explorer has included developer tools since version 8 (reached by pressing the F12 key).

Web applications within Firefox can be debugged using the Firebug add-on, or the older Venkman debugger. Firefox also has a simpler built-in Error Console, which logs and evaluates JavaScript. It also logs CSS errors and warnings.

Opera includes a set of tools called Dragonfly.^[73]

WebKit's Web Inspector includes a JavaScript debugger^[74] used in Safari, along with a modified version in Google Chrome.

Some debugging aids are themselves written in JavaScript and built to run on the Web. An example is the program JSLint, developed by Douglas Crockford, currently senior JavaScript architect at Yahoo! who has written extensively on the language. JSLint scans JavaScript code for conformance to a set of standards and guidelines. Web development bookmarklets and Firebug Lite provide variations on the idea of the cross-browser JavaScript console.

MiniME is an open-source JavaScript minifier, obfuscator, and code-checking tool for the .NET platform.

Pretty Diff is an algorithmic diff tool written in JavaScript for comparing white space compressed JavaScript, and several other languages, to human readable forms of similar code.

Versions[link]

The following table is based on a history compilation forum post,^[75] JQuery author's blog post,^[76] and Microsoft's JScript version information webpage.^[77]

Related languages and features[link]

JSON, or JavaScript Object Notation, is a general-purpose data interchange format that is defined as a subset of JavaScript's literal syntax.

jQuery and Prototype are popular JavaScript libraries designed to simplify DOM-oriented client-side HTML scripting.

Mozilla browsers currently support LiveConnect, a feature that allows JavaScript and Java to intercommunicate on the web. However, Mozilla-specific support for LiveConnect is scheduled to be phased out in the future in favor of passing on the LiveConnect handling via NPAPI to the Java 1.6+ plug-in (not yet supported on the Mac as of March 2010^[update]).^[78] Most browser inspection tools, such as Firebug in Firefox, include JavaScript interpreters that can act on the visible page's DOM.

Use as an intermediate language[link]

As JavaScript is the most widely supported programming language you can run within web browsers, it has become an intermediate language for other languages to target. This has included ports of existing languages, and the creation of new ones. Some of these include:

• Objective-J, a superset of JavaScript that compiles to standard JavaScript. It adds traditional inheritance and Smalltalk/Objective-C style dynamic dispatch and optional pseudo-static typing to JavaScript.
• Processing.js, a JavaScript port of Processing, a programming language designed to write visualizations, images, and interactive content. It allows web browsers to display animations, visual applications, games and other graphical rich content without the need for a Java applet or Flash plugin.
• CoffeeScript, an alternate syntax for JavaScript intended to be more concise and readable and adding features like array comprehensions (also available on JavaScript since version 1.7^[79]) and pattern matching. Like Objective-J, it compiles to JavaScript. Ruby and Python have been cited as influential on CoffeeScript syntax.
• Quby, a proprietary sand-boxed Ruby-like language by PlayMyCode used for building browser games.
• OMeta, a functional language featuring pattern matching.
• Phype, an open source PHP to JavaScript compiler.
• TIScript, a superset of JavaScript that adds classes, namespaces, and lambda expressions.
• ClojureScript, a Clojure to JavaScript compiler which is compatible with the advanced compilation mode of the Google Closure optimizing compiler.
• Parenscript, a Common Lisp library that can translate into JavaScript both well-circumscribed Common Lisp code, and JavaScript rendered as "inlined" S-expressions in Common Lisp source code.
• Py2JS, a subset of Python
• Dart is supported by Google, and compiles to its own native language in addition to a Javascript based one

JavaScript and Java[link]

A common misconception is that JavaScript is similar or closely related to Java. It is true that both have a C-like syntax, the C language being their most immediate common ancestor language. They are both object-oriented, typically sandboxed (when used inside a browser), and are widely used in client-side Web applications. In addition, JavaScript was designed with Java's syntax and standard library in mind. In particular, all Java keywords were reserved in original JavaScript, JavaScript's standard library follows Java's naming conventions, and JavaScript's Math and Date objects are based on classes from Java 1.0.^[18]

However, the similarities end there. Java has static typing; JavaScript's typing is dynamic (meaning a variable can hold an object of any type and cannot be restricted). JavaScript is weakly typed ('0.0000' == 0, 0 == "", false == "", etc.) while Java is more strongly typed. Java is loaded from compiled bytecode; JavaScript is loaded as human-readable source code. Java's objects are class-based; JavaScript's are prototype-based. JavaScript also has many functional features based on the Scheme language.

See also[link]

Computer programming portal

• Ajax (programming) – Asynchronous JavaScript and XML (Ajax), a group of web development methods used to create interactive web applications
• Comparison of JavaScript-based source code editors
• Comparison of JavaScript frameworks
• Document Object Model (DOM) – a convention for representing and interacting with objects in HTML, XHTML, and XML documents
• Dynamic HTML – an umbrella term for a collection of technologies used to create interactive web sites
• ECMAScript – JavaScript is an ECMAScript implementation
• JavaScript engine – a specialized computer software which interprets and executes JavaScript
• JavaScript Object Notation (JSON) – lightweight text-based open standard designed for human-readable data interchange
• JavaScript syntax
• Unobtrusive JavaScript – a general approach to the use of JavaScript in web pages
• Dart – a replacement for JavaScript
• Progressive enhancement

References[link]

Further reading[link]

External links[link]

Listen to this article (info/dl)

This audio file was created from a revision of the "JavaScript" article dated 2011-11-01, and does not reflect subsequent edits to the article. (Audio help)

More spoken articles

Wikibooks has a book on the topic of JavaScript

Wikiversity has learning materials about Topic:JavaScript

• Google's Video tutorials on JS
• Douglas Crockford's video lectures on JavaScript
• FAQ for Usenet's comp.lang.javascript
• Mozilla Developer Center
  • Mozilla's Official Documentation on JavaScript
  • References for Core JavaScript versions: 1.5+
  • overview over new features in JavaScript
  • List of JavaScript releases: versions 1.5+
  • Re-Introduction to JavaScript
• Eloquent JavaScript
• JavaScript – Opera Developer Community
• JavaScript Libraries Comparison Matrix Tool

Brendan Eich
Born	1961 (age 50–51) Pittsburgh, Pennsylvania
Alma mater	University of Illinois at Urbana–Champaign
Occupation	CTO, Mozilla Corporation
Known for	JavaScript

Brendan Eich ( /ˈaɪk/; born 1961)^[1] is a computer programmer and creator of the JavaScript scripting language. He is the chief technology officer at the Mozilla Corporation.

Education[link]

Brendan Eich received his bachelor's degree in math and computer science at Santa Clara University.^[1] He received his master's degree in 1986 from the University of Illinois at Urbana-Champaign.

Career[link]

Eich started his career at Silicon Graphics, working for seven years on operating system and network code.^[2] He then worked for three years at MicroUnity Systems Engineering writing microkernel and DSP code, and doing the first MIPS R4000 port of GCC.^[2]

Eich is best known for his work on Netscape and Mozilla. He started work at Netscape Communications Corporation in April 1995, working on JavaScript (originally called Mocha, then called LiveScript) for the Netscape Navigator web browser.^[3] In 2010, he wrote about JavaScript: "JS had to 'look like Java' only less so, be Java’s dumb kid brother or boy-hostage sidekick. Plus, I had to be done in ten days or something worse than JS would have happened".^[4]

He then helped found mozilla.org in early 1998, serving as chief architect. When AOL shut down the Netscape browser unit in July 2003, Eich helped spin out the Mozilla Foundation.

In August 2005, after serving as Lead Technologist and as a member of the Board of Directors of the Mozilla Foundation, Eich became CTO of the newly founded Mozilla Corporation.^[5]

Political activities[link]

Eich donated $1,000 in 2008 to the campaign supporting California Proposition 8, which was recorded in a public database with Mozilla's name attached,^[6] and many people commented about this donation on Twitter in March 2012.^[7]

References[link]

• Mozilla Futures: Analysis and Proposals (Slides presented at Mozilla Developer Day on February 27, 2004; more detailed than the recent slides cited in roadmap blog)

External links[link]

• Brendan's blog
• Brendan's Roadmap Updates (Mozilla roadmap weblog)
• Brendan Eich on the Gillmor Gang July 2004 and December 2005
• Brendan's Netscape Joke Homepage
• Computerworld Interview with Brendan Eich on JavaScript
• CNET Interview with Brendan Eich
• Tech Luminaries interview with Brendan Eich