zlacker

[return to "AOSP project is coming to an end"]
1. transp+N4[view] [source] 2025-06-12 06:43:16
>>kaladi+(OP)
Hopefully AOSP Pixel device support is merely delayed, not ended, since Pixel is the only way to get Debian Linux ("Terminal") VM + desktop mode support, >>43973395 .

With Apple's ongoing refusal to enable VM/JIT support on iOS and iPad, Google Pixel + GrapheneOS + Debian is a very competitive 2025 offering.

◧◩
2. safety+9e[view] [source] 2025-06-12 08:48:02
>>transp+N4
Wait what? This is a screenshot of 9 short lines of text from the Reddit image server. What is actually going on? Android source is still Apache licensed right? How are these things becoming closed source? What is happening?
◧◩◪
3. jampek+Be[view] [source] 2025-06-12 08:51:55
>>safety+9e
Apache is not copyleft so new versions can become closed source.
◧◩◪◨
4. safety+oo[view] [source] 2025-06-12 10:41:02
>>jampek+Be
You're right, but I am seeing other random Reddit posts that say Google has simply changed their development workflow/branching strategy, and that the claim from the OP is inaccurate.

At the moment we have 200+ upvotes on something that is very light on information, but heavy on confusion. I am just trying to understand what is going on.

[go to top]