I just read an exciting blog post, The meaning of open, on Google’s official blog. It’s by Jonathan Rosenberg, Senior Vice President, Product Management. It started off last week as an in-house post, but “in the spirit of openness” has been released to the world at large. It makes for an exciting read, because it shows that at the top Google has the right attitude towards its products and the technology ecosystem at large.
I found one comment near the start of the post particularly promising:
In many cases we aren’t there, but I hope that with this note we can start working to close the gap between reality and aspiration.
The example that jumped straight into my head is Google Earth, which is one horrible big beast of proprietary software. It’s free to use, but if you want some “advanced” features like the ability to export flyovers as movies you have to fork out hundreds. Anything you export is full of copyright message, compasses, etc. They’re basically having to protect the interests of those who provide that content that we see for free. There’s a notion of openness in that they provide the powerful KML language to do build all sorts of cool things around in it, but as long as the central pillar is closed it isn’t, in my mind, good enough. Well it would seem that the powers that be at Google agree, and these guidelines and Google’s longterm vision dictate that products like Google Earth must eventually come out into the open.
On a related note, the following excerpt also interested me:
There’s also our recent work with the W3C to create a standard geolocation API that will make it easy for developers to build browser-based, location-sensitive applications. This standard helps everyone, not just us, and will lead to users having access to many more compelling apps from thousands of developers.
The reason it interests me is that I’m also not a big fan of Google Maps. Why should developers have to embed some other party’s JavaScript to get a map? I much prefer the idea of an HTML5 tag that enables the platform to display maps in its own way, with the option of complete styling and integration with the rest of the page (like with HTML5’s <video> tag). I’ve been doing some cross-platform mobile work for roam3, and one tiny little bit of work I’ve been doing highlight’s this issue. If you’re doing a cross-platform app written in HTML (using PhoneGap) and you want to insert a map, using the Google Maps API seems ludicrous. Android has built-in map functionality which (as far as I’m aware) you’re unable to use in a webpage, so instead you use a bit of clunky and slow JavaScript to do the job. If there was a generic map tag then the browser would be free to use the operating system’s more efficient built-in alternative (which ironically, in the case of Android, is still Google Maps, but a nice efficient and smooth-scrolling Java version). Anyway, this excerpt gives hope that an HTML5 tag like I’ve described might not be too far away. Perhaps it’s already here, in which case I really should get around to reading up on it.
Those are just two interesting tidbits that caught my attention. I won’t go on about the rest of the post; you’d be better off reading it yourself. The important thing is that Google is demonstrating a very promising attitude towards openness. Free software purists might dislike that this posts alludes primarily to open source, not freedom, but I say forget the terminology: Google is doing a great job of addressing practicalities and issues of freedom alike.
Let’s see what sort of an open world Google might have helped us reach in another five years.
Update: And oh yeah, I reckon Google’s philosophy of letting you easily stop using their products and transfer elsewhere is worthy of mention. The post mentions the example of not getting on a plane that doesn’t have emergency exits. I certainly appreciate GMail’s POP, forwarding, etc, capabilities, and remember how frustrating it used to be that Hotmail didn’t support any of that. Unfortunately, you might not realise a plane doesn’t have emergency exits until it’s crash landed and you’re trying to get off. That’s what it was like with Hotmail. Thankfully I’ve learnt a bit in the years since then.