Linux

48404 readers

1071 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

[email protected]

what are the pros and cons of apt vs flatpak? (lemmy.ml)

submitted 5 months ago by [email protected] to c/[email protected]

73 comments fedilink hide all child comments

target OS is debian or linux mint

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 5 months ago (1 children)

What storage expense? appimage are actually the smallest thanks to their compression.

I'm saying that Flatpaks use more storage for reliability, and that AppImages are less reliable because they rely on system dependencies in some circumstances.

but usually the issue is that you are missing a lib and not that the app itself is less reliable

This is why AppImages are less reliable. Flatpaks either work for everybody, or they don't work at all. AppImages might not work if you're on a "weird distro" or forgot to install something on your system.

And the support channel of yuzu in their discord was full of people having issues with the flatpak that were magically fixed the moment they tried the appimage, due to that issue with mesa being outdated in the flatpak.

Packaging your software with Flatpak does not mean you won't have issues. But when you do have issues, you know they'll be an issue for everybody. So when you fix it, you also fix it for everybody.

For example, the RetroArch package was using an old version of the Freedesktop Platform, which comes with an old version of Mesa. When they bumped the version (just changing it from 22.08 to 23.08), the problem was fixed: https://discourse.flathub.org/t/problems-with-mesa-drivers/5574/3

[–] [email protected] 1 points 5 months ago* (last edited 5 months ago)

Oh I'm very sorry, I didn't see the period before the At the expense of storage space

Flatpaks either work for everybody, or they don’t work at all.

Maybe? I've seen enough people having weird issues with flatpaks that others don't have. One recent example was somebody complaining here that the firefox flatpak took very long start, which I found odd because flatpaks aren't compressed squashfs images and should not be taking long to start up, that's an issue of appimages and snaps instead lol.

Packaging your software with Flatpak does not mean you won’t have issues. But when you do have issues, you know they’ll be an issue for everybody. So when you fix it, you also fix it for everybody.

Another issue that I've noticed with flatpaks is that they are usually built with generic flags, I don't know if this is a requirement or lazy developer, but this is also an issue that yuzu had, the flatpak was built for x86-64 while the appimage was for x86-64-v2 and that had a 8% boost on fps at the cost of people with cpus older than sandy bridge not being able to use it. (Which I mean if your cpu is that old you can't use yuzu anyway).

EDIT: And by weird distro I basically meant nix or musl distros, which I know flatpak works on because it bundles an entire distro basically, while appimage tries its best to be compatible with every distro provided it uses glibc and follows the FHS.

On that there is no dispute that flatpak/snap is your only option.