Google Releases Internal JavaScript ToolsGoogle Releases Internal JavaScript Tools

Developers can now optimize their JavaScript code with tools used by Google's engineers.

Thomas Claburn, Editor at Large, Enterprise Mobility

November 5, 2009

2 Min Read
information logo in a gray background | information

In keeping with its efforts to promote the Web as as a development platform, Google on Thursday plans to release a set of internal JavaScript programming tools as open source software.

Google's Closure Tools were used to create Gmail, Google Docs, and Google Maps, among other applications.

The Closure apps include Closure Compiler, a JavaScript optimizer designed to produce tight, efficient JavaScript, code that, Google claims, has fewer bugs and is easier to maintain. It removes unnecessary code and compacts the rest to maximize speed.

There's also a Firefox extension that works with Firebug called Closure Inspector. It aims to simplify debugging by making optimized code more readable. Firebug is a Firefox extension that facilitates HTML, CSS, and JavaScript debugging in the browser.

The Closure Compiler can be run as a command-line tool, a Web application or a Firefox extension.

The Closure Library is Google's version of a standard class library for JavaScript, the equivalent of STL in C++ or JDK in Java. It's intended for use with the Closure Compiler to allow programmers to focus on writing code rather than utilities or browser abstractions.

Finally, the Closure Templates offer a set of precompiled JavaScript interface components. They're implemented in JavaScript and in Java for client-side and server-side use.

In June, Google open sourced another Firefox extension that complements Firebug called Page Speed, a tool for analyzing JavaScript performance.

Google has focused on speed across its Web applications and has made speed a major goal for its Chrome browser. Speed, for Google, is a competitive advantage.

Google claims that in several benchmark tests, the V8 engine used in Chrome "is many times faster than JScript (in Internet Explorer), SpiderMonkey (in Firefox), and JavaScriptCore (in Safari)."

In a browser comparison conducted on a Mac Pro (dual 2.8 Ghz Quad-core Intel Xeon), between the developer version of Chrome (4.0.229.1), Firefox 3.5.4, and Safari 4.0.3 (6531.9), the v5 benchmark scores -- higher is better -- were Chrome (4465), Safari (2761), and Firefox (365).

information has published an in-depth report on new software models. Download the report here (registration required).

Read more about:

20092009

About the Author

Thomas Claburn

Editor at Large, Enterprise Mobility

Thomas Claburn has been writing about business and technology since 1996, for publications such as New Architect, PC Computing, information, Salon, Wired, and Ziff Davis Smart Business. Before that, he worked in film and television, having earned a not particularly useful master's degree in film production. He wrote the original treatment for 3DO's Killing Time, a short story that appeared in On Spec, and the screenplay for an independent film called The Hanged Man, which he would later direct. He's the author of a science fiction novel, Reflecting Fires, and a sadly neglected blog, Lot 49. His iPhone game, Blocfall, is available through the iTunes App Store. His wife is a talented jazz singer; he does not sing, which is for the best.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like


More Insights