Member Sign In
Not a member?

A Wired.com user account lets you create, edit and comment on Webmonkey articles. You will also be able to contribute to the Wired How-To Wiki and comment on news stories at Wired.com.


It's fast and free.

Sign in with OpenID
Sign In
Webmonkey is a property of Wired Digital.
processing...
Join Webmonkey

Please send me occasional e-mail updates about new features and special offers from Wired/Webmonkey.
Yes No

Please send occasional e-mail offers from Wired/Webmonkey affiliated web sites and publications, and carefully selected companies.
Yes No

I understand and agree that registration on or use of this site constitutes agreement to Webmonkey's User Agreement and Privacy Policy.
Webmonkey is a property of Wired Digital.
processing...

Retrieve Sign In

Please enter your e-mail address or username below. Your username and password will be sent to the e-mail address you provided us.

or
Webmonkey is a property of Wired Digital.
processing...

Welcome to Webmonkey

A private profile page has been created for you.
As a member of Webmonkey, you can now:
  • edit articles
  • add to the code library
  • design and write a tutorial
  • comment on any Webmonkey article
Close
Webmonkey is a property of Wired Digital.

Sign In Information Sent

An e-mail has been sent to the e-mail address registered in this account.
If you cannot find it in your in-box, please check your bulk or junk folders.
Sign In
Webmonkey is a property of Wired Digital.

Open Libraries: What Chrome Is Made Of

When we introduced Google’s Chrome browser, we mentioned how it’s composed of four rather ambitious open source projects: Google Chrome (the browser itself), Google V8 (the JavaScript engine), Webkit (the HTML rendering engine) and Gears (the web developing enhancer).

But of course, there are more than just four open source projects contributing to Chrome’s success. Most of them come from outside Google, too. In fact, there are 25 open-source libraries and APIs responsible for the functions in Chrome. Programmer Peteris Krumins dug into the code and fills us in on how Google reused existing, freely available code libraries to build its browser. Among them:

You can dive into the code of any of these libraries, including the Chrome browser, by heading directly to its site or repository. If you do, you’ll notice Google actually made some changes to some of the source libraries. You’ll be able to tell by looking for a README.google included in the package which will tell you what contributions Google made.

Reusing existing code can be a good thing, especially for open source projects. For one thing, it standardizes how these functions work — at least with the projects who also use the code. Second, the more developers working with these libraries means these small projects get more developers working for these projects including the high-paid brainiacs at Google. More developers and possibly more innovation means these projects drive forward. In the end, it means these features grow more robust, cooler and just plain easier to use.

[via Peteris Krumins]

Post Comment Comments Permalink Print
Reddit Digg

 
Subscribe now

Special Offer For Webmonkey Users

WIRED magazine:
The first word on how technology is changing our world.

Subscribe for just $10 a year