Google’s iron grip on Android: Controlling open source by any means necessary
arstechnica.com
arstechnica.com
I'm not following how that counts as an "iron grip" or monopolistic behaviour.
Given that, it's somewhat understandable that they're moving to a more closed model, sad as it is.
I don’t think either situation is ideal however, but the iOS motivation seems better aligned with my interests.
Last time I checked, the license fees Google receives did not fully cover the development of Android.
A more correct formulation of the title would be "Google's Totally Normal Grip on Google Apps: How Google Decided It Was in Their Best Interest To Give Away A Lot But Not Quite As Much As Before Free Value."
If you use an Android fork, as enabled and allowed by Open Source, you aren't allowed to use Google anything anymore. That's the deal.
Specifically, if you use an android form that doesn't pass the compatibility test suite. There is no vendor that distributes stock android, not even google. Every OEM maintains a fork from the base android distributed by the android open source project.
The thing you aren't allowed to do is fork android in a way that prevents users from installing android apps.
> What you describe is kind of bait and switch. Sure, Google is absolute legal here, doesn’t mean however that is ethically in the right.
If you provide something initially as open source, are you ethically bound to provide future versions of that thing as open source for all of eternity?