I see people hate snap packaging and removing it if their OS support it. Is it because it’s NOT fully open-source or just due to how the technology works?

Update: fixed typos

  • enoent@lemmy.ilwwbs.comEnglish
    48·
    1 year ago

    This threads got lots of good answers, but I haven’t seen it mentioned that snaps sometimes mean reduced functionality.

    Use the docker snap? Sorry, it can only access your home directory so no -v /some/path:/somewhere for you

    Use firefox or chromium and keepassxc? Sorry, your browser plugin won’t be able to talk to your password manager

    And the updates… dear god. In whose mind was it a good idea to show a “firefox is updating, exit now to avoid issues” TWO WEEKS im advance. Closing the app does precisely fuck all unless you manually snap refresh it

    Containerised applications are a fine idea, but snap is a horrible implementation of it

    • VerbTheNoun95@sopuli.xyzEnglish
      11·
      1 year ago

      Didn’t know that about the docker snap but that is insane. It would be straight up unusable at work for me.

    • Fubarberry@lemmy.fmhy.mlEnglish
      4·
      1 year ago

      To be fair, those are both issues with flatpak too. You can change the file system permissions with a command or flatseal, but I don’t know of a fix for the password extension issue.

      • Infiltrated_ad8271@kbin.social
        7·
        1 year ago

        In general the integration of flatpak is quite good (even more if we compare it with snap), but there are still some gaps. In this case there are some solutions like this one.

    • deejay4am@lemmy.worldEnglish
      4·
      1 year ago

      I tried to get microk8s up and running by installing it from a snap since I figured it would be a nice and easy way to get up and running quickly.

      I’ve spent so much time trying to get it working that I haven’t even started to learn k8s yet since I can’t get the damn thing to run.

      I think I’m switching to Debian for my servers.