• Samueru_sama@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    16 hours ago

    However if you want to be taken serious in your criticism please inform yourself on what you’re criticize

    they simply don’t fix the libfuse2 issue

    Fixed 3 years ago

    Neither Flatpak nor Snap run “another distro inside”

    The flatpak runtimes are huge and are another distro in practice, just check the contents of the gnome runtime and you will see it is another distro.

    Flatpak also depends on namespaces which paranoid distros disable and cause issues. Which the person you responded to talked about it and you ignored all together lol

    • Natanox@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      1
      ·
      15 hours ago

      Fixed 3 years ago

      This contradicts their own wiki. Type 2 AppImages do use libfuse2, which is the problem.

      Flatpak also depends on namespaces which paranoid distros disable and cause issues. Which the person you responded to talked about it and you ignored all together lol

      Because it makes absolutely no sense what he said. Even in the github thread you linked it is said that namespaces are enabled by default in the kernel nowadays, and any alternative would be more insecure. With the exception of Ubuntu (which uses Snaps) any major distro either comes with Flatpak already installed or the ability to do so with just 3 commands that do not change anything in the kernel. Like, he got it backwards: you have to disable namespaces (and by doing so break any non-legacy kind of virtualization or sandboxing) by default.

      The flatpak runtimes are huge and are another distro in practice, just check the contents of the gnome runtime and you will see it is another distro.

      I think our definitions vary. What I was thinking about when hearing “another distro” was stuff like Docker, where another kernel, package manager etc. gets loaded. Do you just talk about size?