12
submitted 1 year ago by operator@kbin.social to c/linux@lemmy.ml

So I know my way around Linux pretty well. However I never really got the gist of the difference between Snap, Flatpak and Native packages.

What exactly sets them apart?

Why does everyone seem to hate snap?

I have been using all of them, simultaneously on the same system and never really noticed a difference in the way installation, updates etc are handled (syntax ofc).

I hear snap sandboxes? Is that the main reason? Thanks for your insights..

you are viewing a single comment's thread
view the rest of the comments
[-] frozen@lemmy.frozeninferno.xyz 11 points 1 year ago

Snaps are disliked because the store is closed-source and run by Canonical. Snaps are also disliked simply because Canonical is pushing them so hard, forcibly replacing native packages that exist and work fine. For example, there was a debacle a while back where running apt install firefox still installed the Snap version instead of the native version.

Flatpaks are disliked because they sometimes struggle to integrate into a system well. For example, Discord Rich Presence doesn't work for the Flatpak version of Discord unless the thing you want Discord to detect is also a Flatpak, and even that detection is shaky.

Snaps and Flatpaks are both disliked because they contain frameworks and runtimes that some users consider bloat.

To further explain, when you use a native package, it and its dependencies get installed on your system. If any other package in the future requires one of those dependencies, awesome, it's already there. But for Flatpaks and Snaps, each app has to bundle its own dependencies. Sometimes they can be shared with other Flatpaks/Snaps, depending on the dependency, but they still require at least a little extra storage space.

There are probably details I'm forgetting, but those are the main arguments. My advice is if you're happy with the way your system is running, don't worry about it. My personal preference is Flatpak first, native second, Snap never. I don't have anything against native packages, but some software I use is exclusively distributed as Flatpak, so I switched most things over for consolidation.

[-] ReakDuck@lemmy.ml 3 points 1 year ago* (last edited 1 year ago)

Afaik snaps can't share depending packages, making it store the same dependency multiple times. Flatpak can share the depending package+version, sharing it to every app it needs and store it once.

The Golden advantage I see is not having issues installing multiple versions of the same dependency, which would be kinda hard for a native system depending on the type of package an app is depending on. Like Python and Java could easy have multiple same versions on a native system, but other things may be too difficult to realize except you use Flatpak.

So the main point is comfort I guess, it just works on all distros unrelated if a dependency doesn't exist for the distro or is too old/new.

Not sure how secure Flatpak is. But 2 serious scenarios are existing to use it: You want to isolate the app from system for security. You have an immutable read only OS and want to easily install packages.

this post was submitted on 11 Jul 2023
12 points (100.0% liked)

Linux

48376 readers
1470 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS