- cross-posted to:
- pulse_of_truth@infosec.pub
- cross-posted to:
- pulse_of_truth@infosec.pub
You must log in or register to comment.
Full AOSP compatibility for Pixel devices is a huge reason to buy a Pixel instead of a 3rd party OEM. They’re shooting themselves in the foot.
That is probably a fraction of one percent of the pixel purchases.
Maybe but those 1% of buyers are multiplicators incentivizing others to buy the same phone.
Maybe Google is comfortable enough offering the Pixel as a typical consumer device now, instead of a developer one. They used to be able to differentiate themselves from their competitors, but there aren’t many competitors left.
From the article, Google can technically let AOSP still exist while destroying it in practice:
what could happen is that Google takes Android closed source from here on out, spinning off whatever remains of AOSP up until that point into a separate company or project… This technically means “AOSP is not going away”,
From the author, a sentiment I fully agree with:
If in 2025 you still take statements from big tech based on best intentions, you’re a fool.
This is the reason why I’m not a fan of permissive licenses.
This is the reason why I’m not a fan of permissive licenses.
If Google is the sole copyright holder, a copyleft license would change nothing because they still have the option to change the license going forward.
That is actually a fair point, but I assume out of the millions of lines of code, not all of them come from Google, right?
That would requiere convincing the copyright holders of those lines, or at least rewrite them. The latter I don’t see it impossible, but it would take time.
Still, I will always rather a strong copyleft license…
They’ll just do an Apple and publish the source to the bits they have to while keeping the bits they don’t closed source making the os as a whole closed source.
I don’t understand.
also I thought Apple builds upon BSD style licensed stuff, while Android is on Linux which is gpl?
Doesn’t matter for a distribution, Apple historically also shipped some gpl tools like bash and Samba, they just provide the source for what they have to.
So, basically what they’re already starting to do?
Soooo, that means that android is fucked but custom roms should be able to continue from android 15, not?
The more time goes by, the worse the divergence will be. (I think this is basically the idea, but correct me if I’m wrong:) Right now, we might have GrapheneOS 15 vs Android 16. But eventually, there will be an Android 17 and an Android 18. GrapheneOS developers will either have to trudge along with an older OS, or hire more developers to recreate the missing pieces of the code - pieces Google has already created but will never release . The missing pieces will get bigger and more significant. Android 15 will age out of security updates.
This is pretty bad.
They planned so from the start.
