They are awesome but personally I don't use them. I have an obsession with memory management. Flatpak apps don't share libraries so they get chunky at times. This shouldn't be a problem for most people. It's a personal problem.
this post was submitted on 08 Mar 2024
193 points (94.5% liked)
Linux
48333 readers
430 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
It’s bloated. Not as bad as snap though. xbps for the win
Everything I've gotten as a flatpak has been borked in one way or another. I only use it if there is literally no other option available.
I'm a bit "eh" on flatpak. The only benefit I see is that it's sometimes more up-to-date than what I can get from an LTS package repository. As a heavy CLI user they force me to find and click icons which is irritating (yeah - I know about flatpak run something.I.always.forget but that's even worse somehow).
I've hit occasional issues with applications being too locked-down. Like with Darktable only being able to see things in $HOME/Pictures. But I keep my photography work in a different location so it can't see it. I had to jump through some odd hoops to fix that. Not a problem of flatpak itself per se but something you can expect when dealing with package makers.
I fall back on flatpak if the version available through the standard package manager is too out-of-date for my liking. Other than that I can't be bothered.
EDIT: Okay - for people who think they're being "helpful" by telling me that "aliases are a thing" just stop. I'm not going to workaround a broken system. I'm going to use another one that isn't broken (or less broken).
load more comments
(22 replies)
It's a decent packaging solution.
regarding the sandboxing, all the negatives are present with none of the benefits, wish they'd just rip that shit out
if you want to run software you don't trust, firejail it or get it's snap
My totally unscientific opinion (with a double-your-money-back guarantee!):
I'm not crazy about either Flatpak or Snap for that matter as there's so much backend baggage for both as well as certain hurdles regarding privileges and access to the file system (somebody please correct me if I'm wrong or working with dated information.)
My other completely prejudiced, unfounded bias against Flatpak is that it appears to have been adopted by RedHat as "the one true way," and what with IBM's/RedHat's behaviour anti-FOSS behaviour lately, plus I've almost always have been an apt user, I find it a pill hard to swallow.
Me, say what you will about the security issues and its other flaws, but I like AppImage.
load more comments
(6 replies)