Comment on Google promises a rescue patch for Android 14’s “ransomware” bug
QueriesQueried@sh.itjust.works 8 months agoYou may want to do some research. The first bit is uhhhh… plain incorrect. The chromium based things, sure, I guess that could be said despite it being an open source project and easily forked.
tsonfeir@lemm.ee 8 months ago
I’m gonna flip that around on you. Prove to me that LineageOS, an Android based operating system, no longer pulls in code from AOSP.
QueriesQueried@sh.itjust.works 8 months ago
But the problem is not AOSP, but Google? This reference and forking could be done to any code or math out there, why is it somehow “not ok” only when AOSP comes into play? I personally cannot think of anything that would be a specific halting factor exclusively because it’s AOSP. If your issue is with Google, then find a trustworthy fork that you like. You definitely ain’t alone in hating Google, especially compared to the people developing these alternate OS’s.
All that to say, why are you “flipping it on me” to “prove they no longer pull code from AOSP”, when that wasn’t even the target to hit, or the question.
If your issue is with Google, take issue with Google. Likewise, if your issue is somehow “literally everything Google has ever touched, even if they have no part in it today, or ever again.” Then I got nothing. If you’re that horny on main to burn Google to the ground, start writing your own mobile phone OS I guess, I simply don’t see any other way you’re going to hit that mark.
tsonfeir@lemm.ee 8 months ago
Ahh. I can see you don’t understand. Well, I’ll just go fork some “code and math.”
Have a great night.
QueriesQueried@sh.itjust.works 8 months ago
The entire point is that if such a need arose, you literally could. Either way you still failed to establish an sort of reasoning for AOSP, even a modified version of such, is unusable. If you did that, I wouldn’t have anything else to say. I could disagree with that reason, but it would be understandable.