Slashdot Mirror
Google Open Sources Its Data Interchange Format
A number of readers have noted Google's open sourcing of their internal data interchange format, called Protocol Buffers (here's the code and the doc). Google elevator statement for Protocol Buffers is "a language-neutral, platform-neutral, extensible way of serializing structured data for use in communications protocols, data storage, and more." It's the way data is formatted to move around inside of Google. Betanews spotlights some of Protocol Buffers' contrasts with XML and IDL, with which it is most comparable. Google's blogger claims, "And, yes, it is very fast — at least an order of magnitude faster than XML."
If I was the first to comment this, I would say "Cool!"
It is good that Google has started making more things open source, but they still have a long way to go. Right now they are comparable to Apple, they like open source, make some open source products, but aren't like Red Hat and make everything open source, but I guess we should be glad they aren't like Microsoft where nothing is open source.
Taxation is legalized theft, no more, no less.
How do you "Open Source" a Data Interchange format. There is no source to open? You just specify a format and distribute the specs to your trading partners and there you go. I am getting so damn sick and tired of open source this and open source that. The words "open Source" have specific meaning. It is not a catch all term friendly licensing. So Google published the format it uses to push data around. Big Fuckin Deal. In case anyone is interested. I organize my dvd collection by genre and title alpabetically on a book shelf. Look mom, I open sourced my data storage format. Ridiculous.