• jdr@lemmy.ml
    link
    fedilink
    arrow-up
    22
    arrow-down
    2
    ·
    3 days ago

    Are they still trying to make snap happen?

    It’s not going to happen.

    • thingsiplay@lemmy.ml
      link
      fedilink
      arrow-up
      9
      arrow-down
      2
      ·
      2 days ago

      Snap is already a big part of Ubuntu since years. So what do you mean by “its not going to happen”?

    • Wilmo@lemmy.ml
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      2
      ·
      3 days ago

      Its also for my experience the worst way to use apps.

      The fact that I can’t “update” my software without closing it first.

      Why can I do that with all other package formats? I get it won’t be the new version until I reopen the app but still. Its unnecessary friction.

      Also with the prompting last I used it Firefox couldn’t download anything with it enabled.

      Like you ship Ubuntu with like 4 major snaps including the security center and it hasn’t or hadn’t worked with your shipped snaps for at least a year?

      • atzanteol@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        6
        ·
        2 days ago

        The fact that I can’t “update” my software without closing it first.

        Why can I do that with all other package formats? I get it won’t be the new version until I reopen the app

        Asked and answered.

        • Wilmo@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          1 day ago

          Not really though? Or rather - then answer the other half. Why are flatpaks, deb, rpm, arch, etc. ALL able to update in place? But with snaps we need that sucker closed? It sucks to use like that.

          • atzanteol@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            3
            ·
            1 day ago

            Because the app isn’t updated until it’s restarted.

            Do you think you applied that Firefox security update because you updated the flatpak? Because you haven’t if you left your browser running.

            • Wilmo@lemmy.ml
              link
              fedilink
              English
              arrow-up
              1
              ·
              12 hours ago

              Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good.

              I don’t care if Firefox isn’t updated until I restart it. I just don’t want that terrible workflow:

              Click update all. Firefox is open, therefore won’t update until you close it and click update again.

              Every other package manager: Click update. All apps update. When I am ready to close Firefox it’ll be updated next time I use it.

              • atzanteol@sh.itjust.works
                link
                fedilink
                English
                arrow-up
                1
                arrow-down
                1
                ·
                12 hours ago

                Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good.

                Hence my “asked and answered” response. 🙄

            • brax@sh.itjust.works
              link
              fedilink
              arrow-up
              2
              arrow-down
              1
              ·
              24 hours ago

              The problem is that you have to break your workflow to update shit, or you have to do updates multiple times to work around the things you’re doing.

    • lengau@midwest.social
      link
      fedilink
      arrow-up
      1
      ·
      17 hours ago

      They have been trying to work with the Flatpak people to make it a standard everyone could share. After half a decade of frustration I think they just gave up and decided to do it themselves.