• rand_alpha19@moist.catsweat.com
    341·
    4 hours ago

    I think I’ve landed on Flatpak as my favourite between Snap, Flatpak, and AppImage. AppImage, when it works, is nice though. Snaps are just kind of inconvenient (auto-updates are a no for me) and bloated and the things Canonical are doing as an organization put a bad taste in my mouth.

    • Kusimulkku@lemm.ee
      6·
      1 hour ago

      I’ve had bad experiences with AppImages. For universal format they do a really poor job at that. And it’s a huge step back into Windows direction that you’ll have to manually download, update etc your shit. Makes managing a bunch of apps a pain.

  • NateNate60@lemmy.world
    1522·
    4 hours ago

    Unpopular opinion: snap is not so bad and genuinely useful for many things

    I would rather have a snap than building from source or use some tar.gz archive with a sketchy install script

    • babybus@sh.itjust.worksEnglish
      6·
      41 minutes ago

      I would rather have a snap than building from source or use some tar.gz archive with a sketchy install script

      I agree, but that sounds like false dichotomy to me because snap competes with flatpak.

    • m4m4m4m4@lemmy.world
      22·
      1 hour ago

      some tar.gz archive with a sketchy install script

      I just can’t… like maybe I’m too old and that’s why I still can’t wrap my head around how we went from “./configure && make & make install scripts are almost the de facto way to install software in linux” to “a sketchy install script”. We’re living interesting times at Linux

      • RoyaltyInTraining@lemmy.world
        4·
        1 hour ago

        Last time I ran a corporate-made installer, it caused massive graphical glitches and lock-ups after waking from sleep. It basically gave my system computer-AIDS.

        That’s why I never run scripts which are too long for me to easily understand outside a sandbox. Official distro repositories and Flatpaks are the only sources I have some level of trust in.

      • r00ty@kbin.life
        1·
        42 minutes ago

        I remember those times too. The difference today is that there are so many more libraries and projects use those libraries a lot more often.

        So using configure and make means that the user also has the responsibility of ensuring all those libraries are up to date. Which again if we’re talking about not using binary install, each also need a regular configure/make process too. It’s not that unusual for large packages to have dependencies on 100+ libraries. At which point building and maintaining the build for all of them yourself becomes untenable really. However I think gentoo exists to automate a lot of this while still building from source.

        I understand why binaries with references to other binary packages for prerequisites are used. I also understand where the limits of this are and why the AppImage/Flatpak/snaps exist. I just don’t particularly like the latter as a concept. But accept there’s times you might need them.

    • EtherWhack@lemmy.world
      21·
      2 hours ago

      I’d rather be able to use my web browser uninterrupted without it being updated while using it and be forced to restart it.

      • lengau@midwest.social
        2·
        59 minutes ago

        The updates download in the background and will install when you exit the snapped app. If you really don’t want automatic updates, you can run snap refresh --hold to hold all automatic updates or add a snap name to hold updates for that snap.

        • EtherWhack@lemmy.world
          2·
          44 minutes ago

          Nope. There have been multiple times where I have my browser open, in the middle of something and when I go to open a new tab/window I get a blank screen telling me I need to restart FF to continue.

        • lengau@midwest.social
          5·
          1 hour ago

          A built-in way to have services running (which is why openprinting can make a snap of CUPS but AFAICT can’t make a Flatpak).