I am currently using Linux Mint (after a long stint of using MX Linux) after learning it handles Nvidia graphics cards flawlessly, which I am grateful for. Whatever grief I have given Ubuntu in the past, I take it back because when they make something work, it is solid.

Anyways, like most distros these days, Flatpaks show up alongside native packages in the package manager / app store. I used to have a bias towards getting the natively packed version, but these days, I am choosing Flatpaks, precisely because I know they will be the latest version.

This includes Blender, Cura, Prusaslicer, and just now QBittorrent. I know this is probably dumb, but I choose the version based on which has the nicer icon.

  • db2 ( db2@lemmy.one ) 
    link
    fedilink
    English
    arrow-up
    7
    ·
    3 years ago

    I don’t like flatpak or snap or any of them. System libraries exist for good reason, just because your computer is stupid fast and you have enough disk for the library of Congress a couple times over doesn’t mean you should run a veritable copy of your whole operating system for each program. IMO it’s lazy.

    Sandboxing is a different thing though, if that’s the purpose then it’s doing it right.

    • ebits21 ( ebits21@lemmy.ca ) 
      link
      fedilink
      English
      arrow-up
      5
      ·
      3 years ago

      I have a ton of flatpaks which means packages are shared between them, so no it’s not lazy or a copy of the whole system. It makes a ton of sense for stability.

      Updates are diff’s so downloading and updating is fast. Not entire packages.

      Making every package work with only a certain version of a dependency and hoping it is stable doesn’t make a lot of sense.

      • You’ve just moved the packaging problem from distributions to app developers.

        The reason you have issues is historically app developers weren’t interested in packaging their application so distributions would figure it out.

        If app developers want to package deb, rpm, etc… packages it would also solve the problem.

        • ebits21 ( ebits21@lemmy.ca ) 
          link
          fedilink
          English
          arrow-up
          4
          ·
          3 years ago

          Sure. Except you gain universal compatibility for all distros that have flatpak and aren’t building all the different package formats. Makes it much more attractive for actual developers to package since it’s only done once.

          There’s no right answer here, but there are definite benefits.

          I’ve had many little issues since I moved to Linux years ago, most of which would never have been an issue if flatpaks were there at the time. My experience has been better with them.

          • manpacket ( manpacket@lemmyrs.org ) 
            link
            fedilink
            English
            arrow-up
            1
            ·
            3 years ago

            Makes it much more attractive for actual developers to package since it’s only done once.

            I maintain a few apps that are included into some distributions with no participation from my side apart from tagging what I consider releases in my git repo. How is doing something only once is more attractive as not doing it at all?

            • Because you can make sure it was done right. You don’t have to worry about bugs or other issues being the result of faulty packaging if you’re the one doing the packaging. Plus It makes reproducing bugs easier when everyone’s using the same package, and declaring the flatpak as the official package makes it much more likely that people will use the flatpak.

        • ebits21 ( ebits21@lemmy.ca ) 
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 years ago

          As long as they don’t cause conflicts. You know dependency hell is a thing right? The reason flatpaks were thought up in the first place? Right?

    • DidacticDumbass ( DidacticDumbass@lemmy.one ) OP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 years ago

      I see your point, and I agree. No need to spend resources just because we have them.

      Sandboxing is definitely a benefit, but alas as I am learning I have no control of it’s permissions, so that can potentially go wrong.

      • ebits21 ( ebits21@lemmy.ca ) 
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 years ago

        If you switch everything you can to flatpaks and use distrobox for other apps before you switch you’re pretty close (better than toolbox and recommend layering it if you do switch to Silverblue).

        Anything can be layered onto Silverblue if it can’t be installed another way. I’ve found it works well.

        • DidacticDumbass ( DidacticDumbass@lemmy.one ) OP
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 years ago

          Whoa! Distrobox looks cool! Did this come out on Android first? Seems like something I used to have fun with.

          Damn, there are so many cool software I have never even seen in passing. I mean, I guess anything is possible. Hah.

    • ebits21 ( ebits21@lemmy.ca ) 
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 years ago

      Same. Better stability, frequent updates, no building from aur, and permission management with flat seal are great.

      If you use mostly flatpaks they share packages which means they don’t take nearly as much space overall as single packages do.

      Updates with only downloading diff’s is fast and works well.

      • Random Dent ( CrabAndBroom@lemmy.ml ) 
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 years ago

        I also like them just for the sake of tidiness. Some apps like Steam tend to make a big mess of dependencies all over the place, so it’s nice to have that all contained in one place. It does take up more space but I have a reasonably big hard drive so it’s kind of negligible for me.

    • DidacticDumbass ( DidacticDumbass@lemmy.one ) OP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 years ago

      It seem that whatever problems Flatpaks may have, due to sandboxing, is truly isolated. I think as a non-power user, I do not have strong opinions about any kind of technology, I just enjoy the magic of things working without effort on my part. I will dive deeper as my needs change, but my needs are kind of simple too.

  • Yote.zip ( yote_zip@pawb.social ) deleted by creator
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 years ago

    100%. I just wrote a long post surmising this somewhere, but I’m switching my 5 year old Arch install to something like Debian Stable/Testing because I use almost entirely Flatpaks for my user applications (I would do 100% of them if every app I used had a Flatpak), and it’s really just a much better idea to run bleeding edge on only the stuff you care about instead of an entire system.

  • I’m running Ubuntu now and I’m in Snap hell.

    It works well enough for some very basic apps, but for me personally, Snap has created far more problems than it has solved. With Firefox, for example, it makes it a lot harder to use some extensions, and FileBot is entirely useless without file system access (I mean, that’s the entire point of the program).

    I’ve heard Flatpak is better but my experience is somewhat limited. It could hardly be worse, though…

    • Each snap is mounted as its own filesystem, which is messy for several reasons (try making sense of the output of lsblk on your system). Flatpaks don’t do that, though they sandbox in other ways. There really isn’t a “Flatpak hell”, the worst that can happen is packages that depend on different versions of the same library taking up a lot of storage space, which is a problem with snaps too.

      I still prefer to rely on official repos but I do use a few Flatpaks here and there. But one of the main reasons why I don’t run Ubuntu is because of Canonical’s aggressive pushing of snaps.

  • Daeraxa ( Daeraxa@lemmy.ml ) 
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 years ago

    Nope, don’t like them. Nor snaps. I find the sandbox nature annoying and many developers don’t actually seem to understand it correctly anyway meaning you have to use flatseal etc. Then having to deal with some apps writing config within the sandbox and some writing it outside the sandbox…

    My order of preference is generally I pick the “official” supported version as opposed to any community maintained ones. Then within that:

    • Install via the language’s package manager (cargo, npm, pipx, cabal etc.)
    • Appimage
    • Native package (.deb, .rpm etc.)
    • Plain binary
    • Build from source
    • Snap
    • Flatpak
    • DidacticDumbass ( DidacticDumbass@lemmy.one ) OP
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 years ago

      True. I have run into a lot of dumb issues with sandboxing, mostly in choosing a folder other than downloads for file interaction.

      I have overlooked Appimage, and I will consider it. I am intrigued that you put it before native package. I had not considered using the package manager of the language it is built in, which honestly is probably the optimal way to install a package.

      Alright, I have some reading to do. I love learning new ways to do things. I am glad I asked!

      • Daeraxa ( Daeraxa@lemmy.ml ) 
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 years ago

        There is a bit more nuance to it I suppose - I like Appimages for “complicated” apps, i.e. big GUI apps like Inkscape where I prefer native packages for terminal tools. The nice thing about Appimages is that there just isn’t much in the way of integration and therefore its really easy to just try something out with no risk of installing a bunch of extra dependencies and no way of breaking your system - I use Appimagelauncher for managing them but have been considering swapping to something like Appman/AM.

        The other thing that sometimes puts me off of native packages is having to deal with excessive numbers of PPAs or other repos when they aren’t in the main ones.

      • Daeraxa ( Daeraxa@lemmy.ml ) 
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 years ago

        I’ve just had fewer issues with snaps. Honestly I don’t care for either of them so the difference between them for me is pretty slim but I just find Flatpak to be particularly annoying, Snaps just haven’t caused me any real issues other than polluting my device list with endless loop devices.

  • I use Flatpaks for everything I can. I like how Flatpak keeps apps in a container isolated from my system. Also, Flatpaks contains every lib in every version I need for my installed apps, which means It does not rely on my system libs, and I like It, cause my system libs is to make my system works only.

    Flatpaks are just the future of packaging

    • DidacticDumbass ( DidacticDumbass@lemmy.one ) OP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 years ago

      Great explanation and rationale for using Flatpaks! I hope others with questions see this.

      I understand how people may be annoyed by the redundancy of every app packaging their own lib, but I swear those are measured in kilobytes, and people tend to be so obsessively minimalist it is a non-issue. Then again, minimalist are probably compiling their software.

      • stravanasu ( pglpm@lemmy.ca ) 
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 years ago

        I disagree. The other day I wanted to install some audio app that came in flatpak install format (I’ll check and add the name later). The app was less than 30MB in size, but the installation included 300MB of a previous version of org.freedesktop!

        • DidacticDumbass ( DidacticDumbass@lemmy.one ) OP
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 years ago

          I think that is one time download of a library so the app can run. Also, any other app that needs it.

          It seems to me that the biggest complaint people have with flatpaks are the space it takes.

          I wonder if the blow up in GBs was an early buggy behavior?

  • 0x2d ( 0x2d@lemmy.ml ) deleted by creator
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 years ago

    No, because I don’t have a very powerful computer

    Even if I did, I would still prefer to have native applications because it would be more permissive

  • sleepyTonia ( sleepyTonia@programming.dev ) 
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 years ago

    Probably never. They’re my third option after native packages and built-from-source packages/installs either manually or using the AUR. They’re convenient and the only option I tolerate of those newer package styles (Flatpak/Snap/AppImage), but seemingly having to download a new 800+MB runtime for small 32MB applications is ridiculously wasteful and I wouldn’t touch them if I didn’t have at least a TB of storage.

  • thayer ( thayer@lemmy.ca ) 
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 years ago

    I’m glad to see you’ve gotten a ton of feedback here, and I just wanted to add another comment in support of flatpaks and image-based computing. I’ve been using Linux extensively for about 15 years now, mostly Arch and Debian Sid. I’ve been a distro packager, and I’ve compiled plenty of my own apps over the years.

    This past year I took Fedora Silverblue for a spin after following the project for quite some time, and I am convinced that the image-based system approach, coupled with containerized and sandboxed userspace applications, is the future of Linux for most users. It makes so much sense from nearly all perspectives; whether security, reliability, or flexibility.

    Integral parts of the system are mounted read-only by default. Simple commands can rollback unwanted changes, upgrade to a new distro release, or even sideload an entirely different OS. System updates are automated, as are flatpak updates, and there is little-to-no risk to stability due to the very nature of the essentials-only system images. And if something catastrophic did happen, you’re just a reboot away from rolling it back.

    Consider for a moment the collective energy and time that distro package maintainers must undertake on a weekly basis. Much of it simply repeated by each distro, building the same applications over and over again. Flatpaks are built once and deployed everywhere. Think of the collective potential that could be directed elsewhere.

    Couple this with containers and the choice of distro matters even less. Arch, Debian, Ubuntu and Fedora are just a keystroke away. Yes, you can run containers on any distro of course, but you don’t gain any of the other ostree benefits mentioned above.

    I have since moved all of my workstations to Silverblue and I don’t see myself ever going back to a traditional system again. If anything, I may start automating my own image deployments, similar to Universal Blue.

    Yes, flatpak as a platform still needs some work, and so does ostree, but both are evolving quickly and will only get better with time.

    To others who complain about needing Flatseal…in my opinion, this is a feature to be embraced, not loathed. Sane defaults are rarely sane for everyone, and Flatseal exists to give you complete control over what an app can or cannot see and do.

  • pipyui ( pipyui@kbin.social ) 
    link
    fedilink
    arrow-up
    1
    ·
    3 years ago

    I had fedora installed the last few years, and was digging flatpak… until I wasn’t. One day I ran out of disk space - 230 Gb of flatpak dependencies. I run a pretty slim system, so what the actual heck? Did some research, learned how to flush cached and redundant packages, shrunk my flatpak deps to… 150 Gb

    I’ve since been trying Endeavor

  • vampatori ( vampatori@feddit.uk ) 
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 years ago

    Containerised everything is the future of computing and I think we’ll look back on how we do things currently with horror!

    But yes, I am slowly starting to use more contained desktop applications. Server-wise, everything I deploy is now in containers.