• yaaaaayPancakes@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    3
    ·
    1 year ago

    Flatpack isn’t without its own quirks and flaws. There is no One True Way. Being open-source, there shouldn’t be one.

    It is definitely slow though, mostly on first run.

    • ChunkMcHorkle@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      1 year ago

      Being open-source

      Yeah, that. That’s exactly the problem. To quote @Puzzle_Sluts_4Ever above, who put it much better than I could:

      . . . the main issues boil down to concerns over some parts of the Snap ecosystem being closed source, Canonical’s ongoing efforts to try to get some of the Red Hat “premium linux” money, and arguments that other solutions (e.g. flatpaks and appimages) are “just as good, if not better”. And it doesn’t help that Canonical/Ubuntu is increasingly pushing snap as “the only solution” for some applications.

      When you speak of no single One True Way and things being completely open source, Canonical/Ubuntu have already left the chat.

    • iopq@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      There should be one way for sandboxed shit, since the alternative of package managers already exists

      We don’t need snap, app image, flatpak all to compete. We need shit that just works

    • nick@campfyre.nickwebster.dev
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      Gotta be honest, as a dev I tried to make a Flatpack of my app and gave up. Making a snap was much easier. Of course, I also offer it as a .deb, .rpm, Pacman package, etc. too