• TMP_NKcYUEoM7kXg4qYe@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    10 days ago

    Don’t introduce proprietary crap just so companies can profit off of it.

    I agree but I think it’s the user who should be able to make the informed choice (ie. during installation)

    • FooBarrington@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      10 days ago

      Honestly, why enable this kind of behavior in any way? Any user is free to make an informed choice by installing it themselves.

      We all know how this goes. Once a critical mass is reached, enshittification begins to milk everything dry. By making it an installer option, you’re legitimizing it and supporting a worse future for the Linux desktop.

      • TMP_NKcYUEoM7kXg4qYe@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        9 days ago

        Ok but KDE has official Snap packages so they already are “legitimizing it”. Also snap won’t be able to entshittify anything. Snapd is still open source, so you can just repackage the software for different package system.

        • FooBarrington@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          9 days ago

          My guy. There is no open backend for Snap. If Ubuntu enshittifies Snap, nobody can host an alternate backend for them. How does the client being open source help you?

            • FooBarrington@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              5 days ago

              Okay, and how does snapd being open source help with that? It literally has no effect on it.

              And when your best argument is “if it gets enshittified you can switch off of it”, why help it get popular in the first place?

              • TMP_NKcYUEoM7kXg4qYe@lemmy.world
                link
                fedilink
                arrow-up
                1
                ·
                2 days ago

                Well if it were closed source, it would be harder to repackage proprietary apps because you would not know how the snap “root filesystem” translates to $DISTRO root filesystem.

                Because some apps are only packaged as snaps so if you want them to be accessible to users, you have to install snapd. Flatpak can still be the default which on non-Canonical distros already is. Which why I don’t even worry about snap becoming the standard.

                • FooBarrington@lemmy.world
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  2 days ago

                  Well if it were closed source, it would be harder to repackage proprietary apps because you would not know how the snap “root filesystem” translates to $DISTRO root filesystem.

                  Only if all the other tools (like Snapcraft) were also made closed-source and obfuscated, but that’s besides the point. What if, for example, Snaps start costing money, and you can’t legally turn them into Flatpaks and distribute them? What if the only legal way to get some software for Linux will be the official Snap repository? This approach will make for a far worse user experience than simply using the already working, already open-source and non-enshittifiable alternative.

                  Because some apps are only packaged as snaps so if you want them to be accessible to users, you have to install snapd. Flatpak can still be the default which on non-Canonical distros already is. Which why I don’t even worry about snap becoming the standard.

                  And by promoting Snap to the same status as Flatpaks on other distributions, you’re opening the gates for enshittification and a worse user experience tomorrow. Again, why support it as an equal option if we all know the price?

      • TMP_NKcYUEoM7kXg4qYe@lemmy.world
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        9 days ago

        This is a stupid argument. In FSF’s eyes even having nonfree repository (ie. for drivers) is bad so this is completely irrelevant for anyone considering flatpak or snap. Both have nonfree stuff in there.

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

          Both have nonfree stuff in there.

          But flatpak’s backend is open source and self-hostable, while snap’s is proprietary and not self-hostable. Flatpak is the lesser of evils from this point of view.

          • TMP_NKcYUEoM7kXg4qYe@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            5 days ago

            I’m not arguing whether snap or flatpak is better. Flatpak is better.

            But your arguments are going against each other. You disagree that FSF should tell you what software you can use but then you want to tell other users what software they can use. If you use flatpak despite of FSF’s opinions, you should let people use snap despite of your opinion.