Skip Navigation

Why is snaps hated

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

87 comments
  • I remember when the snap version of calculator took like 12 seconds to launch and Canonical were like "yeah but what's the big deal?".

    It basically turns your super fast Linux into feeling like a 10 year old windows machine.

    I hear they have improved performance now though but there are many other reasons why snap suck.

    • I hear they have improved performance now though

      It's still not great. Better, but still slow enough to make you question whether you've actually launched the app or not.

  • Snaps have centralized control. Canonical has to approve a snap package. Flatpak is like most of Linux. Anyone can make a Flatpak. Also, in my experience, Snaps had a lot of issues early on that were not present in Flatpaks. Now, Flatpak dominates and Snaps kinda feel like a irrelevant runner in a race long after the officials closed competition packed it up and went home.

  • Hmmm, can we just sticky a "snaps are bad" thread? I like to see activity but this same question keeps getting asked.

    Also sticky Red Hat's "response", it should deter most of the neolibs.

  • Snap is not fully open source. It's slower than flatpak, it's centralized to Canonical's servers.Flatpaks so not update by default where snaps do, so if a feature breaking update is released and you haven't disabled automatic updates, you're screwed with snap. Flatpak does not need admin privileges where snaps do.

  • ... No, snaps aren't considered too open source as far as I know. For me it's how it's forced on me almost as hard as a Windows upgrade. I'm pretty sure my next linux distro is PopOS, not Ubuntu.

  • Canonical has a history of ignoring established practices and established software projects in the FOSS community and instead rolling their own in-house competitor behind CLA licensing agreements that make it hard for community developers to contribute. It feels like an embrace-extend-extinguish situation to me. They did it with Unity (replacing GNOME 3), Mir (replacing Wayland), and now Snap (replacing Flatpak). There are also technical reasons why many Linux users don't want these userspace/sandboxed packages (Flatpak and AppImage included) taking over the position formerly occupied by native distribution packages (.deb, .rpm, pacman, apk, etc) because of issues with unnecessary copies of dependencies and poor integration with the rest of the system. These concerns apply to Snap as well, and Ubuntu has been pushing to replace .deb packages with snaps.

  • Not generic as Docker containers, not native as package managers. If I’m trusting an app to install it, then I don’t want to care about security rules.

  • Some of the things that have already been mentioned are true also for me, especially around permissions and assumptions about my system's setup. However what really did it for me was when Firefox stopped recognizing my keyboard after a snap refresh. It's just as if no input device was there for FF anymore. I found reports of the issue, but no solution. In the end I installed from a DEB repository and went through the shenanigans to prevent snap from reinstalling it.

  • Mostly it has to do with how Canonical owns the snap store. if they made it so anyone could build a snap repo then a lot fewer peopl would have problems

87 comments