View Single Post
Capt'n Corrupt's Avatar
Posts: 3,524 | Thanked: 2,958 times | Joined on Oct 2007 @ Delta Quadrant
#3230
Here's a little more controversy for the TL/Android discussion...

Andy Rubin explains why Android is not a Community Driven Project:

http://androidandme.com/2011/05/news...riven-project/

Open source is different than a community-driven project. Android is light on the community-driven side and heavy on the open source. Everything we do ends up in the open source repository.
We're building a platform, not an app. Developers evolve APIs and deprecate APIs, they are always adding new functionality. When we add new APIs, typically in my opinion community processes don't work. It's really hard to tell when you're done, it's really hard to tell what's a release and what's a beta.
Developers have to have an expectation that all the APIs are done and complete at certain date.
If it was a community process, an OEM could start building devices, then those devices would be incompatible from a third-party developer's perspective. We have to make sure those APIs are on all those devices that adopt those platforms. Going forward, that becomes part of our job, our responsibility. A community process harder to manage. We take submissions form community, but it's a much more controlled way in how it comes out.
Have at it.
 

The Following 2 Users Say Thank You to Capt'n Corrupt For This Useful Post: