• RustyNova@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      10 hours ago

      TBH if it’s just for that I’d rather use nix packages. But flatpak’s sandboxed app are better for sus packages or proprietary-might-spy-everywhere packages.

      • wheezy@lemmy.ml
        link
        fedilink
        arrow-up
        6
        ·
        15 hours ago

        I rarely encounter them. But they usually work when I do. But, ugh, they’re just kinda gross. Like, is this a .exe? No thank you. Don’t give me windows trauma.

        • Damage@feddit.it
          link
          fedilink
          arrow-up
          1
          ·
          7 hours ago

          I’m always like, “well, now where do I put this executable?”

          But they do work

          • wheezy@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            2 hours ago

            Clearly in $HOME/Downloads/ and forget that you left it there. Then use app(3).AppImage the next time when you redownload it. Keeps you running the most up to date version. It’s flawless.

    • wheezy@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      15 hours ago

      I’ve had the opposite experience with flatpaks that I have with snaps. I don’t really use them much. But when I see that as an option I use it and it just works. Definitely a fan as a USER of them. I’m sure people have their complaints as users and developers. But I definitely have to say it’s been positive so far. Which is a rare consistency in the life of installing packages.

    • NaibofTabr@infosec.pub
      link
      fedilink
      English
      arrow-up
      28
      ·
      1 day ago

      Flatpaks are better than Snaps, but properly maintained dependency trees and SBOMs are best, by a wide margin.