Linked by Thom Holwerda on Wed 11th May 2011 20:35 UTC
Google It was inevitable, of course, and rightfully so: Google is having its big I/O conference, so we have to talk about the lack of Honeycomb's source code. While not violating any licenses, the lack of source code doesn't sit well with many - including myself - so it only makes sense people are asking Google about it. Andy Rubin confirmed we're never going to see Honeycomb's sources as a standalone release. He also explained what 'open' means for Android.
Permalink for comment 472722
To read all comments associated with this story, please click here.
RE[2]: Comment by vivainio
by Beta on Wed 11th May 2011 22:41 UTC in reply to "RE: Comment by vivainio"
Member since:

Well, that's an odd argument. I mean, isn't the fact that Google is using a *different* approach using *existing* open source code the whole *point* behind open source?

Forking is a large part of FOSS.
But so is upstreaming, the concept of making changes and offering them up to the parent project for inclusion. A few complaints directed at Android have been that it is using a different method for handling 'handoffs' (wakelock), and it's rumoured with 3.1 to have a different USB driver stack to Linux.

This means more work to keep Android in sync with Linux kernels, and that drivers developed for Android devices don't automatically get supported in Linux.

Reply Parent Score: 3