Wondering about Google...
Some years ago, on a technology publishers mailing list, I questioned whether Google's "Don't be evil" slogan had any real meaning. I was immediately rebuked once it was discovered that I hadn't even tried out some of the Google services that were under discussion. But, among the reasons I hadn't tried all the services was that I was wary of the massive agglomeration of information of all types that was accruing within Google's databases and servers. This V'GER-like gathering of all the information in the world that can possibly be gathered into one place, to me, seemed to at minimum lay the groundwork for the possibility of misuse in the future. Not that that's happened (to my knowledge). But still, to me, there's always seemed to be a bit of the "bully" in Google's swagger and its approach to extending its tentacles into new markets. And why do you have to explicitly say "Don't be evil?" Isn't that a given?
In more recent years, quite a few other people have come to find some of the behemoth's actions disconcerting. For example, there was the lawsuit over Google's decision to just start scanning in books and presenting their content online. Some thought that was a bit of overreach, possibly a violation of copyright laws.
More recently, people are wondering about Google with regard to the network neutrality debate. Network neutrality as Google would like it to be enforced turns out to be quite beneficial for the Google business model -- while that same "neutrality" ensures that the transport extremely heavy (in byte size) internet content will be paid for in part by people whose use of the web is quite lightweight.
Next, there's Google Android. Is it Java? What about the Java Community Process? As Simon Morris noted, Android "caused a minor stir" when it was initially launched. It seems to me that the stir has only increased over time.
Terrence Barr points out that "Google's Android philosophy may not be exactly what the developer community and open source advocates was hoping it to be" in his recent post Google Andriod: "Cease and Desist". Terrence points to some news that is apparently surprising many people, namely the cease-and-desist order Google has aimed at Cyanogen. "This is a weird one," says Dan Nosowitz in the Gizmodo post he wrote upon seeing the news. The comments people are leaving are quite interesting too.
Maybe the Cyanogen issue is a bit more serious than Microsoft's attack and subsequent gifting of Mike Rowe over his incredibly threatening MikeRoweSoft.com web site, or the McDonald's fury over one little Malaysian restaurant named "McCurry" (even if the owners were a bit disingenuous in saying the name really stands for "Malaysian Chicken Curry" -- shouldn't it be "MCCurry" in that case?).
Still, for a company that seems to like to barge right into territories that already have established players and rules, and do things the new way, the Google way, making up its own rules as it goes along -- one wonders why they would take such offense when someone wants to use their stuff as a basis for creating something new and unique that Google didn't think of?
Finally, Malcolm Davis just posted a Response to Bruce Eckel's Google Chrome Changes the Game, in which he points out that the road ahead for Chrome is "fraught with perils."
Seems like a lot of people are wondering about Google these days...
If you have ever wondered how to generate a getter and setter automatically using the NetBeans IDE, well view this minicast.
Malcolm Davis has posted a Response to Bruce Eckel