matlag

The kernel update issue on Android is going to be exactly the same for PostmarketOS and for the exact same reason: proprietary firmwares and/or drivers. There is a huge ecosystem for Android today, including apps for so many EU companies, that they would have to re-develop to port them to Linux, or they'll just rely on Waydroid, so you still have to follow Google somewhat, and now you need to maintain both a GNU/systemd/Linux AND a compatibility layer with Android. With a fork of AOSP, you need only the last. From a security and privacy standpoint, Linux was never designed to handle hostile apps designed to aquire as much data as possible. Android has a sandboxing system: an app cannot go and check what other apps you have. A Linux app can pretty much access everything on your system. GrapheneOS adds on top of that storage and contact scopes: you can define a subset of each per app, and they won't see anything else. In an ideal world, it wouldn't matter: everything would be opensource and developed in good faith. In the real world, you still have tons of malevolent apps that people will want to use anyway, so better take that in account.

If the EU would dare, it could totally fork AOSP. Then each country, company, non-profit can build its own mobile OS on top of it.

No. Not that he wouldn’t want to, but he would have fucked it up already.

Years ago, they were the go to solution for databases. No CIO would ever be fired for picking Oracle over competitors regardless the pain that would follow, same as having Windows as the OS on all employees computers. If there’s an issue with the world’s most popular solutxon: “Shits happens, we all know”, if there’s an issue with that alternative solution: “You see what bappens with your toy-thing? Let’s be professional and use a professional solution!”. Years have passed, the alternative slowly made a name for themselves, but OracleDB didn’t evolve much because of inertia and the high maintenance that locks existing customers. So now they’re going all-in on data centres for AI, that means to me the end is near.

It always ALWAYS comes step by step! First they will introduce age “non-real-check”, then they will enforce the check: you have accepted the principle, so what’s the big deal if we actually check it?

Let’s just hope pissing off the judge on mïnute 1 may get them uncomfortable about the rest of the trial.

So, AI will do the same thing as what light extensions already do, but consuming 4GB of RAM and maxing out CPU load?

The fact that so many users go to a fork just because FF can’t get the settings right from the start should be telling! At this stage, every new version, I go through the settings to double check there is no “new feature” I don’t want enabled by default… So yes, I am tempted by Librewolf.

First, there should be a survey on what users actually want, no? Because if no one wants AI and it’s “always a choice”, what you really do is waste considerable resources with as the only results, more settings users have to go through before starting using their browsers.

I was actually thinking whichever company bringing this for the masses will abandon its support 5y later and 25y from now we won’t be able to read it at all, let alone decode the bits.

1 million years? You mean 200 top!