29
Flatpak vs Snap vs Native Packages
(kbin.social)
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.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Flatpaks are great for GUI apps, and have a sandboxing system that allow them to work well on any system that support flatpak. This allows devs to package once run anywhere, saving Dev time! It also has a portals system to allow for better system integration of the granular permissions needed for the app to actually work (nobody wants a truly isolated sandbox for every app).
Snap is less featureful for GUI apps, but work closer to how native packages do. The real issue is the proprietary app store required for it, making non-foss. If you want the same benefits of snap, check out Guix and NixOS both of which have a more cleaner design, and work better IMHO.
I personally prefer appimages. What are your thoughts about it?
@lemminer @fruitywelsh
Appimage is OK but no auto update makes it download and forget type of deal - definitely not for every app
Flatpak - best for me but permissions on some apps make it unusable e.g. gpodder - command for player as flatpak is unable to access MPV installed from repo flatpak etc. - sandboxing (couldn't fix it with flatseal mpv --profile=... not working)
- snaps people love to hate them... no love from me :-)
Repo if it works, is available - the best option
Its use able. I like unified update mechanism and shared package/library/image systems