I am going to go out on a limb and guess you have never owned an android phone. Because your article is oblivious to the actual situation. Delaying the Honeycomb release isn't some sort of strong arm move to kill open source. It will still be released. Just not in the state it is in right now. Which is a heap of hacks hashed together. And now to the big issue. The carriers and phone manufacturers are the only broken link in this chain. They are the ones that are really “breaking” the spirit of open source. Locking down bootloaders and pumping there horrid gui overlays with bloatware that can't be removed. Do some research before next time. It's what real Journalists used to have to do before Liberal Arts majors were all given a keyboard and a Blog.

I'll never understand the defensiveness of fanboys. Yes, delaying Honeycomb is more about getting it ready for public consumption since it was rushed for the Xoom and other tablets. I argued as much in the previous post. But it's also a sign that Google isn't being completely open. Unless you don't know what open source actually means.

What Jordan said is true for the most part. Google is being forced to put constraints on it because carriers are locking down aspects of the OS to benefit themselves rather than the consumers. The problem is the middle man (carriers) between Google and the consumers that exists since Google is not a device manufacturer, they just provide the OS. It would be like Apple coding OS X or Microsoft coding Windows and then providing the source to HP, Dell, Toshiba, etc. to make any changes that they wanted to and load it on their systems. It makes updates incredibly difficult and causes lag in propagating innovation as updates cannot reach phones until the carriers have going through and made their modifications to it. Look at all the phones that are still waiting on Froyo even though the OS has been available from Google for how long? Exactly. Carriers are still trying to hack in their custom gui overlays and bloatware to push out to consumers. With Google putting restraints on things like this it will allow the OS updates to get pushed to carriers more quickly.Say what you want about it, but it is ultimately in the best interest of consumers in general.

Crying fanboy seems to be SOP for most people who get called out. As a developer for Android and IOS I find it humorous to be called partisan. My “fanboisim” stems from awful research and woeful ignorance on the subject. Open Source as a methodology has no set rules or regulations. Android (because it is based upon Linux) operates within the GNU GPL (v2 or v3 depending on who you talk to.). As such the carriers and manufacturers who operate and distribute Android operating phones are subject to said General Public License. But then again I don't know anything about “Open Source”.You seem to be critical of Google over a perceived breach in the spirit of Open Source yet no mention that those actions are a direct result of the carriers and manufactures flying the bird to the consumer. Because they don't care if their awful code negatively effects the consumer. Never mind that an AOSP ROM run on the same carriers phone can double the battery life of a phone. Never mind that an AOSP ROM (Android Open Source Project for a layman such as yourself) can increase performance dramatically.Open Source and whatever “But it's also a sign that Google isn't being completely open.” aren't the same. You just either wanted to slant a piece in a certain way or was completely oblivious to what is actually going on. Not sure which is more of an affront to intelligence everywhere.It's stupid that Google is trying to kill Bing integration into phones . And if it wasn't such horrid a implementation (I have a Fascinate) people might actually care. But their are reasons entire threads on the internet are dedicated to removing every inch of Microsoft out of their phones(Android that is). It's pure and simple crap. But Verizon/Samsung does everything short of frying your phone before you can remove that bloatware.TL;DR version. Research before you type. Or don't be surprised when you get criticized for it.

I'm not being critical of Google at all, you just seem to be getting worked up over me mentioning the Honeycomb delay. I'm not defending the carriers, and I've written plenty before about the Android fragmentation problem. And I'm sorry if you don't enjoy being called a fanboy, but when you start out a comment assuming I'm ignorant that's how it seems.

Yah I realize the carriers are the problem, but I wasn't giving a full rundown of the Honeycomb delay here. That's in past coverage–

Honeycomb had exactly zero to do with DADI's post.

Not sure where Honeycomb fits into that post. Let me rephrase this. The actions being undertaken by Google have exactly zero to do with either being less Open Source or more Open Source. Enforcing an existing rule under the GPL does not a walled garden make. Not even a flower.

[...] with the security of their information than iOS users. And although Google reported it was tightening access to its open source Android OS back in March, our researchers continually spot plenty of opportunities to capitalize on [...]

[...] が 3 月に発表したレポートでは、Google では、オープン ソースの Android OS へのアクセスを制限していたということですが、弊社の調査では、Android [...]