this post was submitted on 23 Apr 2024
68 points (90.5% liked)
Linux
48329 readers
639 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So like... I understand the why behind flatpaks and snaps, but I'm an end-user, and more often than not they just make things more difficult, in my opinion.
They're really great for server setups for sort of keeping each individual application from being able to deeply influence other applications or the root filesystem.
But this means if I installed the Spotify snap (at least when I last tried a few years ago) I had to jump through a bunch of hoops to get it to be able to access my media files where all my music was stored.
So like I said, great for out-of-the-box-server setups where the everything is a little separated from each other (kind of like Docker, from what I understand, but at the app-level? I could be wrong here.) because it helps default security settings and interactions from getting confusing quickly.
However, for your casual end-user, it can quickly become a confusing nightmare if you actually do need your applications more easily interacting with one another because you're just trying to write an email.
Anyway, that's my personal opinion: The reasons they exist server-side are pretty solid, but the reasons they exist on desktops for the end-user are less compelling and often result in user frustration.
I've found the opposite as an end user with Flatpaks. It makes it easy to install an app on multiple devices with different Linux flavours and it'll just work.
Even if you're on a single device, if the app isn't in your repo or the latest version is not available in the repo, then flatpak can be very convenient. Certainly easier than compiling from source.
It is secure in the sense that it runs in a sandboxed environment with its own libraries. The downside of that though is bloat as you will have duplicates of libraries you already have on your system downloaded for flatpak. That bloat diminishes to an extent the more apps you use as the apps will share and reuse the Flatpak downloaded libraries, but your first app could be 2gb just because of the libraries and dependencies.
That bloat also extends to memory - you might be running two copies of multiple libraries at a time - one for the native system and another for the Flatpak app.
So on the one side it's convenient and allows distributions across all flavours of Linux, and it sandboxes apps which is potentially more secure but the downside is bloat, and resource use.
Ubuntu have gone too far with Snap, forcing it instead of providing native apps, and it's proprietary. Flatpak is more open and an option for users rather than forced on them.
Thanks for the really good breakdown. I was familiar with the idea that flatpaks are more open and snaps are more proprietary, but I had less understanding of the details of how they're sandboxed. Thanks again, I'm sure it will help others understand it better, too.
Please don't go anywhere near servers with either of those, that's what docker and alternatives are for.
Try running a stable distro without them. If you want a program not to be years out of date, and don't want to compile everything manually, the only options are to use an alternative package manager (flatpak/snap/nix/etc.), distrobox, or appimage + some pm for updates.
They're a lifesaver for casual users, especially when they're integrated into a gui (software centre and discovery for example). None of the other options are nearly as user friendly.
Permission issues are really rare and distro specific from my experience. Also there are tools like flatseal to make fixing them easier.
I hate snaps and how they pushed them on desktop users, but they’ve always been intended for servers, it’s one of the reasons they can ship things like unified kernel images. Ultimately they allow for a modular immutable system, potentially much more flexible than some others like Silverblue or Fedora Atomic stuff.
What they can do is pretty neat, but their “transitional” deb packages for normal users were ridiculous and should never have happened.
TBH I haven't used snaps but based on info from this thread:
Because of those reasons I wouldn't use it even on a private server, let alone in production.
So does nix, but it also enables declarative package management, adding your own package sources, modifying existing package definitions, creating your own repos, and generating docker images. It also works perfectly fine for userland packages.
Arch mentioned btw
We could just kill snaps on the desktop in favor of flatpak. Oh wait