Comment by good8675309

6 days ago

Personally I'm excited about the death of Android, now resources can be put toward mainstreaming and maturing the Linux Phone ecosystem

Hopefully 2026 or 2027 will be the year of the Linux Phone

Strong disagree. Linux, its permission system and its (barely existent) application isolation are lightyears away from the security guarantees that Android brings.

  • Desktop OSes and their derivatives are woefully behind in this regard, and unfortunately the will to bring them up to par is incredibly weak. Of those in mass use (Qubes OS is neat but its user base isn’t even a rounding error), macOS probably does the most, but it’s still lagging behind iOS and what’s been implemented has come with much consternation from the technically inclined peanut gallery.

    I understand some amount of reticence with commercial OSes, but there’s no justification for being against it on open Linux based desktops and mobile OSes. We really need to get past the 90s-minded paradigm of everything having access to everything else all the time with the only (scantly) meaningful safeguards coming in the form of *nix user permissions.

    • > We really need to get past the 90s-minded paradigm of everything having access to everything else all the time

      I do agree with that, and I strongly believe that the iOS and Android security model is way ahead of Desktop Linux. But what I observe is that nobody seems to care about the security model. A recurrent complaint I see against anything AOSP-based (including Android) is that people "want to be root".

      22 replies →

    • Fun fact - on most Linux distros any user program can see almost any event, yes including key presses, by reading from the right /dev/... file.

      This is not surprising. The desktop Linux community reacted with hostility to the well funded security efforts (selinux, apparmor, grsecurity, etc)

      2 replies →

    • Flatpak and Snaps are built to solve this. They do conflict with some expectations from users to be able to play around with things, though, so they do not have the penetration one might want.

      6 replies →

    • Aren't all the necessary pieces for something better essentially in place now that unprivileged namespaces are well-established?

      They've for sure had more than their fair share of security issues, but those are bugs, not fundamental design problems as far as I understand?

    • Letting everything I install have access to everything is the core feature I want out of a platform. If I can't have that might as well just use android

  • This might be a strange take in these times, but I feel like the browser largely solved the "I need to run potentially adversarial application code in a sandbox". For native applications, stick to stuff that's vetted and in well-maintained repositories, or well-known open source projects that you trust. All of this technical work just to be able to run hostile native code ignores that you don't have to, and probably shouldn't want to, run sketchy code on your device. Installing random untrusted software is bad, even with the most advanced security model in the world. At the very least it will probably abuse whatever permissions it has to spy on you to any degree it can (which is a lot, even for web pages) and to send you advertising notifications.

  • This assumes that the mentioned systems are the only security considerations on a Linux system. Clearly this is not the case so I am unsure why you omit other security-related aspects of Linux here.

    • Android, being based upon the Linux kernel, has all those and its own app permission system built on top. Linux on its own comes nowhere close to this.

  • Android brings malware apps and security fixes that come after months rather than next day compared to GNU/Linux.

    The isolation is nice but not so important once you stop running malware constantly.

  • Not lightyears. About 20 years, which is how long it took Google to pile on the mountain of complexity and inefficiency to accomplish this.

    • Well, we've had containers on Linux for more than a decade now and we're still nowhere near where Android was on day 1.

I.. don't think it will happen. For several reasons too. It is not that I don't think Android will change substantially, but the following constraints suggest a different trajectory:

- AI boom or bust will affect hardware availability - there is a push on its way to revamp phones into 'what comes next' -- see various versions of the same product that listens to you ( earing, ring, necklace ) - small LLMs allow for minimal hardware requirements for some tasks - anti-institutional sentiment seems to be driving some of the adoption

  • I think adoption will hinge on whether existing Android apps will just run on it with something like waydroid/anbox or not.

    Gaming on Linux took off with Proton. Linux on phones might go the same path.

I understand why mobile/tablet OSs are so crappy compared to desktop; in the past these devices had no resources cpu and ram wise and had to heavily watch battery consumption (the latter is still true mostly, but that should be up to the user), but my phone is more powerful than my laptop and yet runs crap with no real usable filesystem and all kinds of other weirdness that's no longer needed.

However, I have 2 Linux phones and Linux on phones is just not there. Massive vendors (Samsung, Huawei, etc) would need to get behind it to make it go anywhere. Also so banking etc apps remain available also on those phones. We can already run android apps on Linux, Windows apps, so it would be a bright future but really it needs injections and support for large phone makers.

I hope the EU/US mess will give it somewhat of a push but I doubt it.

  • FWIW, Nokia did develop a pretty good Linux phone back in the day (Maemo/Meego) with Nokia N9 (it even received rave reviews from consumer tech sites like engadget), but it did get killed off as they got absorbed into Microsoft (we all know that didn't age well).

    Similarly, Palm Pre, and especially HP Pre 3 was a wonderful WebOS incarnation.

    Ubuntu Touch did seem like it had a future, but it was a massive sink for Canonical so it was defunded as well.

    The user experience was there on all of these: the apps, not so much.

    • Ubuntu Touch is not dead though, I use it happily on my primary device for 8 years. It's working like a charm. And waydroid allows you to run APKs, even if some bank apps may not work.

> death of Android

death of personal computing freedom, sovereign compute, and probably soon our ability to meaningfully contribute to the field as ICs?

A lot of really bad things are happening to our field, and Google is one of the agents responsible for much of it.

  • > A lot of really bad things are happening to our field, and Google is one of the agents responsible for much of it.

    I mean, breaking news from 2010, but of course never assume things are so bad that they can’t get worse.

This is one of the most naive things I see people repeat.

The reality is that we're lucky to have mostly-good things at all that align with most of our interests.

Yet people get so comfortable that they start to think mostly-good things are some sort of guarantee or natural order of the world.

Such that if only they could just kill off the thing that's mostly-good, they'll finally get something that's even better (or rather, more aligned with their interests rather than anyone else's).

In reality, mostly-good things that align with most of our interests is mostly a fluke of history, not something that was guaranteed to unfold.

Other common examples: capitalism, the internet, html/css, their favorite part of society (but they have ideas of how it could be a little better), some open-source project they actually use daily, etc.

If only there weren't Android, surely your set of ideals would win and nobody else's.

  • Agreed that there is a ton of baby in this bathwater.

    Also, the open nature of AOSP gave Google its advantage during the early days. Since then, Google has morphed into a company that would likely not make the same decision to create an open-source OS free for others to use and contribute to.

    So in the end, what we as consumers actually get, in 2026:

    - Google encourages application developers to use hardware attestation to prevent themselves from running on non-blessed, third-party AOSP distributions.

    - Google builds basic functionality people care about (including passkeys!) into Play Services, a closed mega-application that happens to require a Google account for most features, and is a moving target for open distributions to mimic.

    - Google has closed AOSP contributions to themselves and OEM partners only. AOSP releases are now quarterly source dumps.

    - OEMs which traditionally allowed bootloader unlocking (and thus actual ownership of the hardware) have removed it as a matter of policy.

    So what exactly is open about Android anymore? Does "source-available OS you can see and not touch" align with your interests? Because it's increasingly not aligned with mine.