{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihwagpk4ioszvbncjib7gczbyfyodkihgovn6yhb4fw6dks2ocdva",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mi3b6nprthr2"
  },
  "path": "/t/choice-of-choosing-a-linux-distro-for-a-advanced-linux-users-is-very-limited/35726?page=2#post_35",
  "publishedAt": "2026-03-27T23:21:36.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "Cyber-Typhoon:\n\n> GrapheneOS working great with hardened_malloc doesn’t really contradict anything. It actually proves the point. GrapheneOS is a tightly controlled environment. Same dev behind it, same allocator, same stack, everything built and tested together. Of course it’s going to be smooth there.\n>\n> Desktop Linux is just a different world. You’re mixing:\n>\n>   * apps that expect different allocators (jemalloc, PartitionAlloc, etc.)\n>   * different packaging systems (system, Flatpak, snap)\n>   * tons of hardware and configs\n>\n\n>\n> That’s where things start falling apart.\n\nI think I get where you coming from, but I wouldn’t agree that “GrapheneOS is a tightly controlled environment. Same dev behind it, same allocator, same stack, everything built and tested together.”\nBecause the Android application platform is totally independent from GrapheneOS and still 99% of apps can run on it with hardened mallow and memory tagging.\nThe dev’s of GOS haven’t changed anything about how Android app’s run, and Android app dev’s don’t make any changes to their apps to run on GOS.",
  "title": "Choice of choosing a linux distro for a Advanced Linux users is very limited"
}