Hacker News new | ask | show | jobs
by _bxg1 2899 days ago
AOSP's position is nothing like that of Linux. For years now it's been held hostage by a mega-corporation that doesn't really want it to be open-source any more. Google didn't buy and build Android and then make it free out of idealism, they did it so Apple couldn't become a monopoly and lock Google search out of mobile. Now they've more than accomplished that, and if they had their way it would already be proprietary.

Probably what Pichai is talking about is charging a fee for Google Play Services, not AOSP. Although if they did decide to proprietize all future development work on AOSP, it would be interesting to see how the community would respond. It's possible we'd see a major fork and a revitalization of community work a la Linux, instead of the little garage forks we mostly have today.

1 comments

Google is already well in the process of making everything they can proprietary. Browser, Calendar, Camera, Dialer, Gallery, Music Player, SMS and probably more - all left to basically bitrot in AOSP while Google pushes proprietary replacements as part of the gapps bundle loaded onto OEM phones.

The core of Android may be open source, but between so many API's being shoved into Google Play Services and AOSP apps being all but abandoned the writing is on the wall.

Exactly. They actually go one step further than that with the Google Services API's. Things like notifications and location can now go through the proprietary API's instead of the system ones, with special perks. This means that if you don't have Google Services, then even if you get your hands on a third-party APK without using the Play Store (hard enough as it is), things will sometimes just randomly break because API's are missing.