The big one is Apple’s new Advanced Data Protection. It’s very new, and it isn’t on by default, but that was a killer feature that brought me to Apple I don’t necessarily trust Apple any more than I’d trust Google, but the ability to E2E encrypt my cloud-backed data out of the box is something Google will likely never do.
But I bet most users will never even know that exists.
Google is really the only reason I won’t consider Android for anything. Time and time again they’ve proven themselves to be untrustworthy. Sure, Apple may collect your data, but their entire existence isn’t about selling that data to advertisers. I wish there were more options.
The last time I tried to use a degoogled phone it was basically impossible. Authy isnt on any other store, updating apps was a pita, notifications didn’t work half the time because too many damn apps rely on Google’s push notification system…
You 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.
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.
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.
Lemmy loves google, but I’m with you. I don’t use any of their products or services. People here say, “why not just buy their product and use other software?”
That’s still buying their product. And their software still lies within the offshoots.
The big one is Apple’s new Advanced Data Protection. It’s very new, and it isn’t on by default, but that was a killer feature that brought me to Apple I don’t necessarily trust Apple any more than I’d trust Google, but the ability to E2E encrypt my cloud-backed data out of the box is something Google will likely never do.
But I bet most users will never even know that exists.
Google is really the only reason I won’t consider Android for anything. Time and time again they’ve proven themselves to be untrustworthy. Sure, Apple may collect your data, but their entire existence isn’t about selling that data to advertisers. I wish there were more options.
Have you heard of graphene OS? Because this decouples Google and you still have an android phone.
So… buy a google product and install other software on it? That’s still supporting google. I can understand why someone would not want to do that.
You can purchase a non Google phone and put graphene OS on it…
The last time I tried to use a degoogled phone it was basically impossible. Authy isnt on any other store, updating apps was a pita, notifications didn’t work half the time because too many damn apps rely on Google’s push notification system…
That’s still supporting Google and letting them dictate where technology goes. The same with using chrome, or anything chromium.
You 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.
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.
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.
Ahh. I can see you don’t understand. Well, I’ll just go fork some “code and math.”
Have a great night.
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.
Lemmy loves google, but I’m with you. I don’t use any of their products or services. People here say, “why not just buy their product and use other software?”
That’s still buying their product. And their software still lies within the offshoots.