• lengau@midwest.social
    link
    fedilink
    arrow-up
    5
    ·
    9 days ago

    I don’t like snaps because it’s just another Canonical NIH thing. Everyone else agreed on flatpak which seems to have a good design with portals and all and being fully open.

    Snaps both predate flatpak and do things that Flatpaks are not designed to do.

    Canonical have also been a part of the desktop portals standard for a very long time, as they’ve been a part of how snaps do things.

    • Laser@feddit.org
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      9 days ago

      Snaps both predate flatpak and do things that Flatpaks are not designed to do.

      By less than a year judging by the article… and for individual applications, there was AppImage.

      Snaps can do things flatpaks can’t do. Which is true but also kind of irrelevant if we’re talking about a means to distribute applications in a cross-distribution manner as opposed to a base system A/B partition solution.

      Or am I misunderstanding?

      • lengau@midwest.social
        link
        fedilink
        arrow-up
        3
        ·
        9 days ago

        The claim that snaps are a Canonical NIH thing is falsified by those two facts. Even if Canonical said “okay, we’ll distribute desktop apps with Flatpak,” that wouldn’t affect the vast majority of their ongoing effort for snaps, which are related to things that Flatpak simply doesn’t do. Instead, they’d have the separate work of making the moving target of flatpaks work with their snap-based systems such as Ubuntu Core while still having to fully maintain that snap based ecosystem for the enterprise customers who use it for things that Flatpak simply doesn’t do.