I don’t really care about all these different things, as long as none of them become a crazy confusing mess, like Windows DLLs.
this post was submitted on 07 Jul 2025
694 points (92.5% liked)
Linux
56269 readers
755 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 6 years ago
MODERATORS
I'm relatively new to Linux. I honestly don't see what the problem is.
It destroys the beautiful and carefully cultivated ecosystem of distributed packages that has been the bedrock of Linux for decades. They're bloated, often not quite as sandboxed as claimed, have created packaging chaos, and assume availability of system services that may not be there.
load more comments
(1 replies)
I'm not a huge fan of Flatpaks, they're a lot harder to distribute offline versus something like AppImage. Seriously, you have to like create an offline repository, then create a bundle, and it's like 6 or 7 steps, it's honestly kind of ridiculous lol but other than that they seem fine, and they're easy enough to update (but so are apt packages)
I know some people may say "oh why do you need that", but Linux has taught me that my computer is my own, and I should be able to use it the way I want to. I shouldn't have to fight with my package manager to get it to do what I want. So I guess you could say, no I'm not really a fan of Flatpaks.
Personally, I didn't mind Snaps, but I'm getting kind of really fed up with especially for-profit companies etc so I don't like Snap that much now either.
Apt packages are nice, but the more of them you have installed, especially if you're using Ubuntu-based distros and have lots of PPAs, the more annoying upgrading your distro version can be because of all the dependencies and cross-dependencies.
AppImage tends to just work for me, as long as it's not compiled with a newer libc-bin version than the distro I'm currently using has, and I really enjoy that it's just one file I can copy and run pretty much anywhere.
I seem to have constant issues with AppImages. Every single one I have currently won't open. I get an error message relating to either qT or GTK. Tried searching for the error and get a bunch of old forum threads talking about either not being compatible with Wayland at all, or comments stating that the one specific AppImage in question must have been "packaged badly". Thankfully, nothing 'mission critical' for me is an AppImage currently, but it is quite upsetting that I have the most problems with the supposed "just works" app packaging/distribution option.
load more comments
(3 replies)
Can someone explain why flatpak isn't necessary for distros that have proper OS dependency management like Arch-based distros or Nix?
Seems like flatpak is solving a problem for OS's that don't have proper dependency management.
You answered your own question. Arch and Nix solve the same problem Flatpak solves, but by using better dependency management. Flatpak’s main proposition is built-in sandboxing and convenience, but if you’re on an “expert” oriented distro like Arch (btw), you probably don’t care as much about those “freebies.”
In that case flatpak is basically a hack for OS's with broken or improper dependency manangement systems. Either those OS's should fix their broken systems, or ppl should move to OS's that do it properly, as that's one of the most important functions of your OS anyway.
Also pretty much everywhere you're using flatpaks (or snaps or...), you are doing it on top of a Linux system that's still getting its core system updates via traditional dependency management. And flatpaks, despite trying not to, make assumptions about your kernel, your glibc version, architecture, ability to access parts of your filesystem or your devices, that can break things, and doesn't bother to track it.
And the closer you get you tracking that stuff (like Snap tries to), you hilariously just get back to where you started, with traditional dependency management that already exists and has existed for decades.
load more comments
(1 replies)
load more comments
(1 replies)
I've never heard anyone say that Flatpaks could result in losing access to the terminal.
My only problem with Flatpaks are the lack of digital signature, neither from the repository nor the uploader. Other major package managers do use digital signatures, and Flatpaks should too.
Nah, it's the same as with systemd, docker, immutable distros etc. Some people just don't appreciate the added complexity for features they don't need/use and prefer to opt out. Then the advocates come, take not using their favorite software as a personal insult and make up straw-men to ridicule and argue against. Then the less enlightened of those opting out will get defensive and let themselves get dragged into the argument. 90% that's the way these flame wars get started and not the other way around.
For the record, I use flatpak on all my desktops, it's great, and all of the other mentioned things in some capacity, but I get why someone might want to not use them. Let's not make software choice a tribalism thing please. Love thy neighbor as thyself, unless they use Windows, in which case, kill the bastard. /s
I was just wondering the connection between flatpaks and the terminal because I’ve never heard of flatpaks before and Wikipedia says they’re a sandboxed package management system or something?
As someone who uses Flatpak you can still use the terminal to install, uninstall and do maintenance, not sure why people believe terminal is useless with Flatpak 😞
Flatpaks are containers, same as Snaps, I personally prefer Flatpaks over Snaps, but just my personal choice. I use Flatsweep and Flatseal apps to help administrate Flatpak apps, but use terminal as well 🙂
load more comments
(2 replies)
Flatpaks are awesome. Flathub is awesome. :)
I like the idea of them because I don't like dealing with dependencies changing and breaking stuff and I don't really care too much about disk space in the context of non-game desktop apps, as I don't tend to install lots of them.
That being said I absolutely hate that permissions are all over the place and flatpak doesn't ship a GUI to manage them by default, nor do you get any indication as to what permissions a program has until you try some functionality (like filesystem or camera access) only to find out it doesn't work out of the box.