• 0 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle














  • It’s usually easier to criticize something than to go through the effort of understanding it. Posts like the OP are an example of that.

    … And ironically, your post is doing the same thing here with software packaging:

    The biggest conceptual change in packaging has been “waste as much disk as you like duplicating dependencies to avoid conflicting dependencies”,

    Nobody is perfect, so it’s important to keep an open mind about things, especially when one don’t understand them, and especially² when one thinks they understand them as it’s always possible to be wrong (unless they don’t care about going through life as an ignorant asshole. Plenty of people thrive like that.)



  • If you’re new to Linux, then your probably not familiar with the full Linux community yet. Much like in real life, online Linux spaces tend to have a very loud minority of conservatives who hate progress.

    Usually you’ll see them hating on things like systemd, 64bit architectures, containers, new packaging systems (like Flatpak), immutable and experimental distros (like Nix), Wayland, “bloated” desktops like KDE or Gnome, and much more.

    And just like in real life, the antidote is to not take another person’s word for it. Do your own homework/try things out yourself and arrive at your own conclusions.




  • This is FUD. It definitely is not a “critical” security feature. Firefox flatpak can’t currently do its own internal sandboxing of subprocesses via namespaces, but it does do seccomp bpf filtering. That’s in addition to the standard sandboxing of flatpak itself, which is implemented using namespaces anyways.

    If you are extra paranoid, you can tweak the flatpak’s permissions to harden the sandboxing via your distro’s flatpak settings app.