Why Google loves open source

Google has been a huge beneficiary of open source over the years, building its infrastructure on the freely available software. But it has only been in the past year that Google has gone on a serious open-source charm offensive, both contributing actively to open-source projects and calling out its significant contributions to open-source projects: over one million lines of code each year in addition to serving as a host to over 160,000 open-source projects.

Now Alan Noble, head of Engineering for Google in Australia and New Zealand, has called out the various benefits Google derives from open source:

At Google, we love open source for a few reasons. First, it speeds innovation. Open source lowers the barrier to entry for users, website owners, and application developers. It means there can be another Google, or another Yahoo!, started from someone's garage in Auckland or Arhus with very little capital required, because the building blocks for success are freely available.

It also reduces inefficiency. In the past, developers wasted time and resources to write web code to cover basic functions common to most websites-like registration pages.

Nowadays, thanks to open code-sharing initiatives, developers don't need to waste time reinventing the wheel. Moreover, as more sharing of code occurs, weaker solutions are weeded out in favor of more robust models.

And finally, it makes economic sense. Although it may sound counterintuitive to give something away for free, the resulting popularity and innovation pays off....We quickly realised that making our code freely available would encourage innovation and new products, and by extension, increase use of our maps. Today, Google benefits by letting thousands of developers around the world innovate on and extend the reach of our products; those developers benefit by never having to build or pay for a platform on which to build.

I used to chide Google for not contributing more actively to open-source projects. No more. The company has resolved that deficiency, and then some. It has become one of the greatest beneficiaries of the open-source development community: a company to be trusted to "not be evil" with regard to open source.

Perhaps that's because Google apparently recognizes that open source isn't something to be strip-mined. For open source to succeed, it must be made into a renewable resource. That means contributing back. It means respecting the community and feeding it.

Google groks this. The next phase is to convince enterprise IT to contribute back, too, as it is the group most in need of the cost savings, innovation, and efficiency that open source can provide. Red Hat CEO Jim Whitehurst has been calling for greater enterprise IT participation in open-source communities. Let's hope they listen.

[gstein67]

Google's Open Source efforts started four years with the launch of code.google.com and the first Google Summer of Code. Google was also the first platinum sponsor of the Apache Software Foundation ($100k donation per year!), and is a major sponsor of the Open Source Labs at OSU. Then stop and look at the other various grants and conference sponsorships around Open Source.

I don't work there any more, but I'm still amazed at how many people failed to see the numerous ways Google contributed to the community. Maybe they should have had more press releases and self-congratulator blog posts? ;-)

[odubtaig]

As my sister likes to remind me, you have to draw attention to the things you've done. After all, the people who get the most recognition in the workplace are those most vocal about what they have done regardless of whether they've done the most.

[Matt Asay]

I agree with the comment below, but I would also suggest that the comment above also slightly misses the point. Yes, Google did all those things, but what most of us wanted was commensurate *code* contributions, given all that Google pulled from open source. It's now doing that, and then some.