Developer

Google decides to dominate javascript libraries

With each passing day Google begins to look more and more like a Trapper Keeper. The latest move for the Web behemoth is to store commonly used javascript libraries with Google AJAX Libraries API.

With each passing day Google begins to look more and more like a Trapper Keeper. The latest move for the Web behemoth is to store commonly used javascript libraries with Google AJAX Libraries API.

The premise is that many sites serve the same common javascript libraries — prototype, jQuery, MooTools, script.aculo.us and dojo — and performance would increase if these libraries were served from a central place. Naturally Google believe they are the best choice as a point of control.

The obvious benefit is reducing redundancy in a user's browsers cache — not having an individual copy for every site that implements a lightbox would be nice. But Google is also offering some other sweeteners as well:
- Minimal file size: as well as gzipping the library, Google will minify it too. That means no comments and verbose variable naming has been stripped down within the library, all in an effort to lower the traffic served up
- Distributed serving: by serving from Google servers, chances are that users can get the file for a server closer to them than whenever your server is, especially useful for international users.
- Automated updating: easily serving up the latest library may be risky in major version bumps, but for a security update it would be a major boon to have the latest library automagically updated for you.

Further details on the launch of Google AJAX Libraries API (GALA anyone?) available here.

Below is the video explanation:

About Chris Duckett

Some would say that it is a long way from software engineering to journalism, others would correctly argue that it is a mere 10 metres according to the floor plan.During his first five years with CBS Interactive, Chris started his journalistic advent...

Editor's Picks

Free Newsletters, In your Inbox