Feeds

Google unleashes internal JavaScript tools

Channel the power of Gmail

Boost IT visibility and business value

Google's critical mass online, combined with recent years' Web 2.0 fever, have helped consolidate 14-year-old JavaScript in the field of web development.

Now Google has released some of the tools it used to build Gmail, Google Docs, and Google Maps that helped in that process of establishing JavaScript as a central player in the line-up that is AJAX.

The giant Thursday released a compiler, library, and set of templates it calls Closure Tools. The tools have been released under an open-source license, although Google did not say what license.

Google did say, though, that the Closure Tools have grown to be a key part of the JavaScript infrastructure behind its web applications.

"We're particularly excited (and humbled) to open source them to encourage and support web development outside Google," Google said on its blog. "We want to hear what you think, but more importantly, we want to see what you make."

The tools are designed to make the task of building and maintaining the notoriously complex JavaScript faster and more simply.

This is Google's second such offering, following development and maintenance of JavaScript in different browsers with Google Web Toolkit (GWT). The difference is that GWT lets you build JavaScript applications in Java while Closure Tools are for JavaScript.

The Compiler removes dead code and rewrites and minimizes what's left to run fast on browsers' JavaScript engines. "The compiler also checks syntax, variable references, and types, and warns about other common JavaScript pitfalls," Google said. You can compile code through a text box or a RESTful API.

The Closure Library provides something akin to a standard JavaScript library - generally lacking in JavaScript - to build large, complex web applications. The library is server-agnostic and designed to be used with the Closure Compiler. Google said the library: "Provides clean utilities for common tasks so that you spend your time writing your app rather than writing utilities and browser abstractions."

Closure Templates can be used in JavaScript or Java for the client or server and have been precompiled to produce what Google called "efficient" JavaScript. The Closure Templates use a simple syntax that Google said is "natural for programmers." ®

The essential guide to IT transformation

More from The Register

next story
Intel's Raspberry Pi rival Galileo can now run Windows
Behold the Internet of Things. Wintel Things
The Return of BSOD: Does ANYONE trust Microsoft patches?
Sysadmins, you're either fighting fires or seen as incompetents now
Munich considers dumping Linux for ... GULP ... Windows!
Give a penguinista a hug, the Outlook's not good for open source's poster child
Microsoft cries UNINSTALL in the wake of Blue Screens of Death™
Cache crash causes contained choloric calamity
Eat up Martha! Microsoft slings handwriting recog into OneNote on Android
Freehand input on non-Windows kit for the first time
Linux kernel devs made to finger their dongles before contributing code
Two-factor auth enabled for Kernel.org repositories
prev story

Whitepapers

5 things you didn’t know about cloud backup
IT departments are embracing cloud backup, but there’s a lot you need to know before choosing a service provider. Learn all the critical things you need to know.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Build a business case: developing custom apps
Learn how to maximize the value of custom applications by accelerating and simplifying their development.
Rethinking backup and recovery in the modern data center
Combining intelligence, operational analytics, and automation to enable efficient, data-driven IT organizations using the HP ABR approach.
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.