2 ms·
AFAIK the idea isn't that you can't ship devices running other operating systems but that you can't ship devices running non-compliant forks of Android, which I
by saurik 4y ago
AFAIK the idea isn't that you can't ship devices running other operating systems but that you can't ship devices running non-compliant forks of Android, which I do agree is nigh unto the same thing--as Android is open source and that's a decision Google already made--but I think is worth noting explicitly as others sometimes see it as different (both because it doesn't prevent a greenfield alternative, and as Google gave away Android for free and arguably didn't have to--though I kind of think they originally did to pull off the coalition--and so this is one of the ways they maintain ecosystem control without being closed source, which they arguably could just do now without issue... I mean, they've already gone back hard on the level of openness they started with, and for a year or so around Android 3.x they were closed source, which I have oft claimed was to stifle Amazon).
- oblio 4y ago> I mean, they've already gone back hard on the level of openness they started with From what I understand, AOSP is not dead, but it's definitely far behind the latest versions of Android. The default apps are not updated, the UI toolkit is behind, most of the new services used by everything in Android are the proprietary bits. It's basically Darwin at this point, yeah, open source, but in no way shape or form if you build Darwin, do you get Mac OS.
- saurik 4y ago(By "gone back hard" I don't mean "has returned to" but "did a 180 away from". Maybe you are just expanding, but it sort of sounded like you were disagreeing, when in fact I am fully on board. I remember when they started and their stated goal had been to separate all of their build and hosting infrastructure from Google so everyone was working with and seeing live commits to collaborate.)
- tomcam 4y agoMore periods next time plz