• qaz@lemmy.worldEnglish
    18·
    2 hours ago

    Fun fact: there used to be an Authy flatpak that just installed the snap inside

    • renzev@lemmy.worldEnglish
      7·
      1 hour ago

      Oh, what the fuck!?

      TBH I wouldn’t mind it that much. The whole point of flatpak is that the developer can do whatever demented satanic rituals they want inside of the sandbox, and it won’t contaminate the rest of the system.

    • bdonvr@thelemmy.club
      1·
      2 hours ago

      Yep. I’m selfhosting it now. Works great but selfhosting isn’t straightforward yet, still the best Authy/Google/Microsoft Authenticator drop in replacement with sync.

  • rand_alpha19@moist.catsweat.com
    561·
    7 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.

    • Magicalus@discuss.tchncs.deEnglish
      1·
      1 hour ago

      I used to use flatpak for everything, but I just dont have the hard drive space to store duplicates of my graphics drivers.

    • Kusimulkku@lemm.ee
      15·
      4 hours 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.

      • renzev@lemmy.world
        2·
        55 minutes ago

        The thing with appimages is that they expect the developer to have full knowledge of what libraries need to be bundled with their app, which makes it difficult to make truly universal appimages. In flatpak you just select one of a set list of runtimes and add any additional dependencies on top of it. Flatpak also re-uses the files for each runtime in between the different apps that use it, which saves a lot of disk space.

      • Samsy
        3·
        3 hours ago

        But isn’t appimage the closest one to the app-system from Android? Since things could be really different on many clients an “app-container” is the best solution.

        Why not containerise everything? You need libreoffice? No problem, here is a docker or podman container.

        BTW. I like flatpak, too. It’s the most stable, but I never understand it’s mechanics. There is always another pack installed, freecode, gtk, qt whatever. Even if the system has already the correct gtk version, nope, the dev decided to use the gtk image from Ubuntu.

        • renzev@lemmy.world
          3·
          1 hour ago

          Why not containerise everything? You need libreoffice? No problem, here is a docker or podman container.

          Flatpak is basically GUI-optimized containers. It uses the same technology (namespaces) as docker and podman, just with some extra tools to make GUI-related things work properly. That’s why flatpak apps don’t use the system’s gtk version – they’re running in a sandbox with a different rootfs. You can spawn a shell into the sandbox of a specific app with flatpak run --command=sh com.yourapp.YourApp and poke around it if you want to.

        • Kusimulkku@lemm.ee
          1·
          2 hours ago

          I’m not too familiar with whatever Android is doing with apks these days tbh. I just don’t like how AppImages fails at the one thing it should do (universality) and doesn’t have the repo model built in. You can have third party solutions to that but it’s just not the same experience.

          Why not containerise everything? You need libreoffice? No problem, here is a docker or podman container.

          I’ve heard people suggest such a solution. Everything is a container and stuff is just exported out so that it shows up to the system like a normal program. Can’t really say I’m the right person to judge the pros and cons.

          There is always another pack installed, freecode, gtk, qt whatever. Even if the system has already the correct gtk version, nope, the dev decided to use the gtk image from Ubuntu.

          It can be both good and bad and sometimes it’s necessary. The whole system relies on being able to use different versions of libraries. But having them as separate packs can help in that programs can share those packs so as a dev you can just target one common base and have your stuff work everywhere. And sharing those runtimes has the benefit of someone else keeping it up to date while you can just test if the updated version works for you and switch to that if it does and so on. And with deduplication, runtimes and stuff share the parts that are common to both afaik.

          It’s a bit more complicated than just shoving everything in but also it’s less work than same thing having to be packaged separately for every distro.

  • NateNate60@lemmy.world
    1724·
    7 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
      21·
      4 hours 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
      322·
      4 hours 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
        6·
        4 hours 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·
        4 hours 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.

      • elidoz
        10·
        5 hours ago

        obligatory “there is always a relevant xkcd”

        • lengau@midwest.social
          6·
          4 hours 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).

    • EtherWhack@lemmy.world
      21·
      5 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
        3·
        4 hours 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·
          4 hours 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
            2·
            2 hours ago

            That is the behaviour that’s built for when an upgrade through a “classic” package manager (e.g. apt, dnf) updates Firefox while it’s still running. The only way I can think of that you’d get that with a snap is if you’re intentionally bypassing the confinement (e.g. by running /snap/firefox/current/usr/lib/firefox/firefox directly, which can also massively mess with other things since Firefox won’t be running in the core22 environment it expects).

            If you’re using the snap as expected (e.g. opening the .desktop file in /var/lib/snapd/desktop/applications/, running /snap/bin/firefox or running snap run firefox), snapd won’t replace /snap/firefox/current until you no longer have any processes from that snap running. Instead you’ll get a desktop notification to close and restart Firefox to update it, and two weeks to either do so or to run snap refresh --hold firefox to prevent the update (or something like snap refresh --hold=6w firefox to hold the refresh for 6 weeks). Depending on what graphical updater you have, you may also have the ability to hold the update through that updater.

            Are you sure you’re running the Firefox snap? Because that sounds pretty much precisely like the expected behaviour if someone had gone to lengths to avoid using the snap.