Google's motivations in protecting its Honeycomb source code are understandable to Slashdot blogger and consultant Gerhard Mack, who notes, "they are worried their code won't be stable on other devices. Unfortunately, they are underestimating what the community could do for them if they opened up the code. There are plenty of hobbyist programmers who absolutely love to mess with phones and would check in fixes as needed."
The company's recent announcement that it would delay the distribution of its Honeycomb source code to outside programmers, most notably, has tarnished Android's "open" image in more than a few eyes.
So, too, have the "non-fragmentation clauses" Google's reportedly been adding to Android licenses, giving it the right of approval for any changes made to the Android code.
Bottom line? Enquiring minds in the Linux blogosphere are wondering whether Android is really open anymore.
Fragmentation has long been a criticism of Google's (Nasdaq: GOOG) Android mobile platform, but until recently, its reputation for openness had been relatively undisputed.
Of course, it's not hard to be seen as open when your principal competition comes from Cupertino. On the other hand, recent decisions in the Googleplex are making that distinction less and less clear.The company's recent announcement that it would delay the distribution of its Honeycomb source code to outside programmers, most notably, has tarnished Android's "open" image in more than a few eyes.
So, too, have the "non-fragmentation clauses" Google's reportedly been adding to Android licenses, giving it the right of approval for any changes made to the Android code.
Bottom line? Enquiring minds in the Linux blogosphere are wondering whether Android is really open anymore.



