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.
Thread beginning with comment 472707
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by vivainio
by mrhasbean on Wed 11th May 2011 21:25 UTC in reply to "RE: Comment by vivainio"
mrhasbean
Member since:
2006-04-03

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?


Well it might be if their *different* approach is shared with others. I was under the obvious misconception that the whole idea of opensource was to share ideas around so that others could also benefit and didn't have to reinvent the wheel. Obviously in Google's case they don't want anyone else building on or benefiting from their closed "opensource" projects.

Reply Parent Score: -6

RE[3]: Comment by vivainio
by JAlexoid on Wed 11th May 2011 23:29 in reply to "RE[2]: Comment by vivainio"
JAlexoid Member since:
2009-05-19

And how exactly are they stopping anyone from using the fruits of their labour in Android? It's the same argument that is applied to Ubuntu - "Wahaha!!! They are successful and they don't push their changes to us".

Reply Parent Score: 3