• bjorney
      link
      fedilink
      151 year ago

      It’s a package format that bundles all required libraries, that way you don’t run into the issue with program A requiring library version <1.1 and program B requiring library >1.3.

      It leads to larger binaries because these dependencies are bundled, but it solves the issue with old/minimally maintained software not working on new OS versions because they depend on an ancient version of libssl or something.

    • @RmDebArc_5@lemmy.mlOP
      link
      fedilink
      5
      edit-2
      1 year ago

      Snaps is Ubuntu/Canonicals proprietary package format which is mostly considered a worse alternative to flatpak (another package format) with no real advantages on desktops that Canonical is trying to force on users

          • bjorney
            link
            fedilink
            2
            edit-2
            1 year ago

            The webserver that canonical uses to distribute other people’s snaps is, and that’s it. APKs aren’t proprietary just because Google runs the Play store.

            If you don’t want to interact with canonical’s servers you can download the snap files from literally anywhere else and install them manually so you don’t have to touch a single line of non open source code.

    • @noodle@sh.itjust.works
      link
      fedilink
      61 year ago

      Cause Snap is proprietary and the repo is controlled only by Canonical/Ubuntu. Flatpack on the other hand allows for third parry repos. And then one might even preference a classical install because ironically its snappier - faster - especially on oldee setups

      • But you can install multiple app stores, right? This is just one. My understanding is that it also adds sandboxing to any snaps you installed.

        • @Kusimulkku@lemm.ee
          link
          fedilink
          21 year ago

          Snaps have sandboxing but only on Ubuntu I think. Flatpaks have sandboxing too but that should work in every distro.

      • bjorney
        link
        fedilink
        21 year ago

        Snap is not proprietary.

        The snapcraft webserver backend is closed source but everything snap adjacent that touches your computer is open source, and you can distribute snaps and install them without using the snap store

    • @Artyom@lemm.ee
      link
      fedilink
      2
      edit-2
      1 year ago

      They are 1. Slow on launch and on boot. 2. Very opaque and offer little control. 3. They don’t integrate well. 4. Proprietary. 5. Probably most importantly, Canonical has made 0 progress and demonstrated 0 interest in improving issues 1-4.

  • @XEAL@lemm.ee
    link
    fedilink
    21 year ago

    What the did with Firefox is a war crime…

    BUT, the other day I had to instal DBeaver and using snap was for sure the easiest/fastest way

  • ShaunaTheDead
    link
    fedilink
    1
    edit-2
    1 year ago

    You can just choose not to use it. They still release everything through their regular repositories for now.

      • @uis@lemmy.world
        link
        fedilink
        01 year ago

        I don’t know how they suck and didn’t use them. I install everything either from ebuilds or build myself.