@Sandra@easrng@haskal That's because Apple is actively hostile to it. You can't publish GPL licensed applications on the iOS App Store without every contributor to the code agreeing to a special exception to the GPL. Apple's terms explicitly say you can't distribute the application outside of their app store among other ridiculous restrictions which are incompatible with the GPL.
@haskal Don't get me wrong, sandboxing applications is generally good. But relying on that in lieu of trusting application developers is a technological solution to a social problem.
@haskal "open-source apps aren’t necessarily more private or secure. Instead, you should rely on the strong security and privacy guarantees provided by a modern operating system with a robust sandboxing/permission model, namely modern Android, GrapheneOS and iOS."
So, trust your proprietary operating system (bad idea) to deal with your lack of trust in the developers of the applications you use... instead of, you know, just trusting the application developers?? 🙃
@Seirdy@haskal I don't think cleaning up the mess of Android wouldn't benefit Google. But apparently it isn't a big enough benefit to upset their business partners.
@Seirdy@haskal IIUC by the time AOSP gets to vendors, the vendors are already starting with a Linux fork that is a few years outdated. That's a bad way to start working on a driver if you want to upstream the driver.
@haskal Security Man says forced obsolescence is about Security. Who cares that it means people need to buy way more hardware? I mean, those lazy application developers need to upgrade their shit. Nonono, don't blame Google for forking the shit out of Linux and encouraging rampant GPL violation by their hardware partners. Google's boots taste too good for Security Man!
@jgoerzen@codeberg@ck IME a code comment is often even better. Many times when I'm in a code review discussion and the code doesn't end up changing, the outcome of the discussion is a code comment.