Rauschmayer - The Past, Present, and Future of JavaScript
Here you can read online Rauschmayer - The Past, Present, and Future of JavaScript full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Sebastopol;CA, year: 2012, publisher: OReilly Media, Inc., genre: Home and family. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:The Past, Present, and Future of JavaScript
- Author:
- Publisher:OReilly Media, Inc.
- Genre:
- Year:2012
- City:Sebastopol;CA
- Rating:3 / 5
- Favourites:Add to favourites
- Your mark:
The Past, Present, and Future of JavaScript: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "The Past, Present, and Future of JavaScript" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Rauschmayer: author's other books
Who wrote The Past, Present, and Future of JavaScript? Find out the surname, the name of the author of the book and a list of all author's works by series.
![Nicholas C. Zakas [Nicholas C. Zakas] - Professional: JavaScript® for Web Developers, Third Edition](/uploads/posts/book/121419/thumbs/nicholas-c-zakas-nicholas-c-zakas.jpg)
The Past, Present, and Future of JavaScript — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "The Past, Present, and Future of JavaScript" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Font size:
Interval:
Bookmark:
Beijing Cambridge Farnham Kln Sebastopol Tokyo
If you purchased this ebook directly from oreilly.com, you have the following benefits:
- DRM-free ebooks use your ebooks across devices without restrictions or limitations
- Multiple formats use on your laptop, tablet, or phone
- Lifetime access, with free updates
- Dropbox syncing your files, anywhere
If you purchased this ebook from another retailer, you can upgrade your ebook to take advantage of all these benefits for just $4.99. to access your ebook upgrade.
Please note that upgrade offers are not available from sample content.
Over recent years, JavaScript has seen an impressive rise in popularity. Initially, that popularity was fueled by the success of client-side scripting, but JavaScript is increasingly being used in a general-purpose capacity, e.g. to write server and desktop applications. This article examines the JavaScript phenomenon from three angles:
We conclude with .
In 1995, Netscapes Navigator was the dominant web browser and the company decided to add interactivity to HTML pages, via a lightweight programming language. They hired Brendan Eich to implement it. He finished a first version of the language in 10 days, in May 1995. Its initial name was Mocha which was changed to the more Netscape-esque LiveScript in September. In December, Netscape and Sun had a licensing agreement that led to the programming languages final name, JavaScript. At that point, it was included in Netscape Navigator 2.0B3.
The name JavaScript hints at the originally intended role for the language: Suns Java was to provide the large-scale building blocks for web applications, while JavaScript was to be the glue, connecting the blocks. Obviously, that shared client-side responsibility never transpired: JavaScript now dominates the browser, Java is mostly dead there.
JavaScript was influenced by several programming languages: The Lisp dialect Scheme gave it its rules for variable scoping, including closures. The Self programming language a Smalltalk descendant gave it prototypal inheritance (object-based as opposed to class-based).
Because JavaScript was supposed to support Java, Netscape management demanded that its syntax be similar to Javas. That ruled out using other existing scripting languages such as Perl, Python or TCL. However, even though JavaScripts syntax is similar to Javas, ]
After JavaScript came out, Microsoft implemented the same language, under the different name JScript, in Internet Explorer 3.0 (August 1996). Netscape decided to standardize JavaScript and asked the standards organization Ecma International to host the standard. Work on a specification called ECMA-262 started in November 1996. The first edition of ECMA-262 came out in June 1997. Because Sun (now Oracle) had a trademark on the word Java, the language to be standardized couldnt be called JavaScript. Hence, the following naming was chosen: ECMAScript is the name of the standard language, its implementations are officially called JavaScript, JScript, etc. Naturally, when talking unofficially about either the standard or its implementations, one mostly uses the term JavaScript. The current version of ECMAScript is 5.1, which means the same as ECMA-262, edition 5.1. That version has also become an ISO standard: ISO/IEC 16262:2011.
ECMA-262 is managed and evolved by Ecmas Technical Committee 39 (short: TC39). Its members are companies such as Microsoft, Mozilla, or Google, which appoint employees to participate in committee work three names among several: Brendan Eich, Allen Wirfs-Brock (editor of ECMA-262) and David Herman. TC39s work includes discussing the design of upcoming versions via open channels such as a mailing list.
Reaching consensus and creating a standard is not always easy, but thanks to it, JavaScript is a truly open language, with implementations by multiple vendors that are remarkably compatible. That compatibility is made possible by a very detailed and concrete specification. For example, it often uses pseudo-code to specify things. The specification is complemented by a test suite called test262 that checks an ECMAScript implementation for compliance. It is interesting to note that ECMAScript is not managed by the World Wide Web Consortium (W3C). TC39 and the W3C collaborate wherever there is overlap between JavaScript and HTML5.
It took JavaScript a long time to make an impact. Many technologies existed for a while until they were discovered by the mainstream. This section describes what happened since JavaScripts creation until today. Throughout, only the most popular projects are mentioned and many are ignored, even if they were first. Two examples: the Dojo Toolkit is listed, but there is also the lesser-known qooxdoo, which was created around the same time. And Node.js is listed, even though Jaxer existed before it.
1997 Dynamic HTML. Dynamic HTML allows one to dynamically change the content and appearance of a web page. That is achieved by manipulating the Document Object Model (DOM) of the page: changing content, changing style, showing and hiding elements, etc. Dynamic HTML appeared first in Internet Explorer 4 and in Netscape Navigator 4.
1999 XMLHttpRequest. This API lets a client-side script send an HTTP or HTTPS request to a server and get back data, usually in a text format (XML, HTML, JSON). It was introduced in Internet Explorer 5.
2001 JSON, a JavaScript-based data exchange format. In 2001, Douglas Crockford named and documented JSON (JavaScript Object Notation) a Lisp-like idea to use JavaScript syntax to store data in text format. JSON uses JavaScript literals for objects, arrays, strings, numbers, and booleans to represent structured data. Example:
{ "first": "Jane", "last": "Porter", "married": true, "born": 1890, "friends": [ "Tarzan", "Cheeta" ]}Over the years, JSON has become a popular lightweight alternative to XML, especially when structured data is to be represented and not markup. Naturally, JSON is easy to consume via JavaScript.
2004 Dojo Toolkit, a framework for programming JavaScript in the large. The Dojo Toolkit facilitates programming in the large by providing the necessary infrastructure: an inheritance library, a module system, an API for desktop-style graphical widgets, etc.
2005 Ajax, browser-based desktop-class applications. Ajax is a collection of technologies that brings a level of interactivity to web pages that rivals that of desktop applications. One impressive example of what can be achieved via Ajax was introduced in February 2005: Google Maps. You were able to pan and zoom over a map of the world, but only the content that was currently visible was downloaded to the browser. After Google Maps came out, Jesse James Garrett noticed that it shared certain traits with other interactive websites. He called these traits Ajax, an acronym for Asynchronous JavaScript and XML. The two cornerstones of Ajax are: First, loading content asynchronously in the background (via XMLHttpRequest). Second, dynamically updating the current page with the results (via dynamic HTML). That was a considerable usability improvement from always performing complete page reloads.
Font size:
Interval:
Bookmark:
Similar books «The Past, Present, and Future of JavaScript»
Look at similar books to The Past, Present, and Future of JavaScript. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Discussion, reviews of the book The Past, Present, and Future of JavaScript and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.