I use flatpak for all GUI apps I use.
this post was submitted on 17 Feb 2024
174 points (94.4% liked)
Linux
48329 readers
639 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
Flatpak usually ships very outdated drivers.
I've been in the support channel for yuzu linux, and you would not believe all the issues people have with games freezing, etc that are instantly fixed by using the appimage instead of the flatpak.
Also flatpaks are non-xdg compliant, since it creates the useless ~/.var directory. And they have said over and over that they won't fix that. So fuck them.
Not to mention all the issues people have with their theming and integration into the system.
Appimages are just simpler and better, the other day I was thinking how many issues would be fixed if Steam shipped as an appimage.
- It would allow for shipping a patch glibc with EAC
- It would allow for moving all the nonsense that steam puts in the home user dir, since appimages support a portable home.
- It would allow for shipping the 32bit libraries instead of having to install them system wide.
And depending on how you go about, appimages will even take less disk space than flatpaks or native packages even though you don't get shared libraries with those, because they are compressed which reduces their size significantly.
Like for example the LibreWolf appimage is 110MiB while a the native package for librewolf 300MiB. Same with LibreOffice, the appimage is 300MiB while the native package is 600 MiB.
It also makes it easier to downgrade if you run into an issue, like I had to had an older appimage of ferdium because the latest version is affected by an electron bug that broke its zoom functionality.
Interestingly I've currently crashing issues with running CS2 through Steam native on NixOS, while the Steam flatpak works like it should.
The part about drivers is true though, as GPL is the reason I'm using native Steam.
You don't have steam-runtime instead of steam-native on nix?
I mean the native NixOS package of Steam (instead of flatpak), not that the Steam package uses native libs.
I believe Steam on NixOS always uses the Steam runtime, because NixOS isn't FHS compliant, thus apps wouldn't find any libs. No, I don't think there's steam-native on NixOS.
I like Flatpak, especially now that it has upstream providing packages. It does not have auto updates yet as far as I know. Not a big deal, if there are important security updates in the news, it is time to check for updates.
Problem I have with Flatpak is their way of naming packages which makes them very akward to run in a WM. That's basically the only reason why I haven't used Flatpak since I switched to WMs, pacman and AUR also work really well so there isn't even a reason to use something else.
Unless you are using like a 64GB drive, not really. Ig flatpaks are as bit more annoying to start from the terminal