Google Exec Hints At Future Open Platform
rsmiller510 writes "At the recent Web 2.0 Summit, Dave Girouard, who is president of Google's enterprise division, stated that his company's long-term goal is to open up the Google development stack to outside developers. If this is true, then it could have some serious long-term implications for developers who could use Google services in new and interesting ways."
I read the entire article. Can I have my five minutes back please?
Summary of article:
Google Exec: We're going to open.... The box! ...
People: Open what?
Google Exec: The box! With... the wires, and blinky lights, and stuff in it!
People: What's in the box?
Google Exec: New and interesting things!
People: O RLY?
Google Exec: YA RLY!
People:
Google Exec: Oh look, pretty shiny...
#fuckbeta #iamslashdot #dicemustdie
he means they'll track all my personal information and use it to their advantage... then count me in!
Allowing everyone to help out with Google's product development is a smart strategy because of how difficult it is becoming to keep up with software enthusiasts who like to collaborate on open source projects. It will be interesting to see how Google will be able to harness the power of collaborative development in their core products.
There's a danger with the word "open", as it carries such good connotations for us here. However, just because we like "open" doesn't mean that whatever is coming from Google is going to match our expectations, let alone our desires.
You have to remember that Google is a very different beast to RedHat for example. Google's business M.O. is like that of no other corporation, so it's hard to draw comparisons, but nobody would ever suggest that they are "an open source company" (not even close), despite the many open source projects that they host, promote, support, and of course use. At best, they are a "somewhat open source friendly" company, and undoubtedly they also know that being open is becoming increasingly important, so they're responding to that.
Note that Google's main products are all closed, and most of them possess a few annoying "features" that would have been fixed by now if they were an open source company --- I'm sure that we can all point to some "feature/bugs" that irritate us personally. :-) In fact they're not even very good at responding to popular feature requests (almost apathetic), so true wide-scale openness is really a long way off for Google.
Given the above, I think that some caution is required when interpreting highly non-specific words spoken by Google execs. While we would like them to become massively more open, their openness may not come in a form that the FOSS community would find particularly attractive. In particular, any thought that Google is going to cede huge amounts of control over to open source developers is almost certainly sheer fantasy.
"The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
Android was supposed to be an open mobile phone OS. But now it seems that it's "open" for reading, not writing or executing. That is, you can look at the source code, but you can't write any changes to your phone. The firmware locks out any OS software that doesn't match the checksum or something. That lockout gives Google control of the Android OS, which means the phones are not open, and Google can even lock out apps it doesn't like, or keep features like remote shutdown (by Google, not by you), even if you want to delete that "feature".
How about Google just opens the Android platform, by allowing the phones to run even altered Android OS versions? Then I'll start believing Google when it claims to "open" some other platform even more likely to stay closed, because it runs on their own hardware, not mine.
--
make install -not war
Google has been opening up their platform already; App Engine gives developers (some) access to GFS, BigTable, auto-scaling magic, etc.