this post was submitted on 11 Jul 2023
164 points (92.7% liked)
Linux
48256 readers
883 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
No, because I don't have a very powerful computer
Even if I did, I would still prefer to have native applications because it would be more permissive
I am totally ignorant, do flatpaks use a lot more processing?
They can take longer to start up, which can suck on older hardware. It's not as bad as it used to be though. Once they're running there shouldn't really be any difference. The main drawback is actually that Flatpaks use more storage space.
I am glad that the startup times have improved, that bodes well for future startup times. Using up more storage really is what makes it suck for everyone. I thought that it was more efficient, since I see a lot of .platform, and I assumed those are libraries shared across flatpak apps that use those dependencies.
I am almost sure AppImage has the same problem? I don't know, people do rated that better though.
Storage space mostly isn't as bad as it is with AppImages. Each AppImage stores all the libraries it needs, even if they are shared with another one. They can't even know if they have shared libraries. A single AppImage will probably actually use less storage than a single Flatpak if you only have one, just because the AppImage only uses exactly the libraries it needs, while Flatpaks use shared sets of them. That being said, Flatpaks generally get less bad the more of them you use, because of the shared libraries. They're still a whole extra set of libraries on top of your system ones though, plus they put out a new set every year. Apps that are still under active development generally get updated to the latest version, but older apps that are basically finished often require older libraries, so that's more space used. Overall for a one off program when you're not using universal packaging systems regularly AppImages are mostly better, but if you're going to be using them regularly Flatpak quickly becomes far better. It still uses more storage space than just using native apps though.
Another difference between Flatpak and AppImage is that it can be kind of a pain to theme Flatpaks to match the rest of your system, and I don't know of any good way to do it with qt6 apps yet, but it's just straight up impossible to theme AppImages. They can technically have themes built into them, but unless you're using Adwaita, or maybe Breeze if you're lucky, they just don't, and having to rebuild your own custom AppImage completely defeats the main benefit of using AppImages.
That is what I thought, and I was confused about people complaining about the redundancy. Also, every new program I install manually seems to pull a crap-tonne of new dependencies, so nobody is saving space.