Here’s Why Google Is Holding Honeycomb Back
gigaom.com
gigaom.com
Of course there will be droves of handset makers releasing crappy handsets with Honeycomb that is not ready. But perhaps one company out there might do something innovative and useful, and that's what you get when you open thing up.
Open always means tons of dreck, but it sometimes means something unexpected and good, that's the whole point. If Google doesn't want tons of dreck, it can stop pretending to be open.
It is a very, very bad sign when somebody is in a social environment and will not share their code. It means they are insecure, it might mean they're not getting any work done. It always means that the code is in a state where they are not proud of it and aren't comfortable receiving feedback. It typically means that the code isn't getting a whole lot better.
A major software company like Google, or a team within that company, can't be compared to a lone cowboy coder. There are perfectly legitimate reasons to hold back code. In this case, though, if this is really the reason - that Honeycomb was rushed to market and the code just doesn't look good, we'll fix it later and let you know - how does that make the relationship with the open community look? Not good. It's not good to be afraid of community feedback, whether you're the Android team or a fresh programmer in an unfamiliar shop.
And as for me personally, it doesn't give me a lot of hope for a pleasant experience on the Honeycomb development I'm going to be doing soon.
Multiple vendors means that the blame gets shifted to whoever holds the most mindshare. In this case, it's Google, since they're trying to provide both a platform, and a brand. Apple pulls it off through vertical integration, and their version of OSS is providing a big box of parts you can strap together to build your own, not to post-mod their thing. It removes all doubt of who's doing what.
Personally, I don't think it's that big of an issue if Google has to alpha/beta it in private before releasing to the general dev community. It's just somewhat snide to use complete and total openness as a selling point, when it's simply unfeasible to be completely open on technical, marketing and design standpoints from day one.
I guess the answer is they aren't.
RIM's decision to jump on the Android train reeks of desperation, they just want to have app count, not quality experience or functionality.