this post was submitted on 20 Oct 2025
917 points (98.8% liked)
linuxmemes
27837 readers
436 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Both of these two cases are why Flatpaks are so attractive.
They work most of the time and I liked them, until I installed my first app that did not work because of the container thing and learning about and using flatseal ate so much of my time, that I never did it again.
I only use yay to install stuff now. And if not on AUR I make (copy and adjust existing) my own PKGBUILD, or find one on a random page of a user who did not publish to AUR yet.
Flatpaks are better than Snaps, but properly maintained dependency trees and SBOMs are best, by a wide margin.
PopOS fucked me up with flatpaks
Gateway drug
They are extremely effective at preventing PackageKit updates on my steam deck
I'm going to be honest to you, I prefer appimages.
I like appimages that are packages on AUR installed and updated using yay, so that I never ever learn that it is in fact a appimage disguised as repo package.
I respect your wrong opinion
I rarely encounter them. But they usually work when I do. But, ugh, they're just kinda gross. Like, is this a .exe? No thank you. Don't give me windows trauma.
I'm always like, "well, now where do I put this executable?"
But they do work
I stick them in /home/bin/ like I would for a compiled app. I found a forum for mint saying thats the expectation for user apps with no specific install location, which is pretty much the issue, anyway.
Clearly in $HOME/Downloads/ and forget that you left it there. Then use app(3).AppImage the next time when you redownload it. Keeps you running the most up to date version. It's flawless.
plus that extra defense-in-depth layer of a sandbox
They take up so much fucking space though
Are you running on a really space constrained system? I Used an old Chromebook with only 16Gb of storage for a bit, and to me it's kinda fun to figure out alternative solutions and applications that can make a system like that work. But when I've got a system with 500GB+, I say who cares about the space packages take up.
Flatpaks are okay for stuff that doesn't need deep access but they don't work for many things.
TBH if it's just for that I'd rather use nix packages. But flatpak's sandboxed app are better for sus packages or proprietary-might-spy-everywhere packages.
I've had the opposite experience with flatpaks that I have with snaps. I don't really use them much. But when I see that as an option I use it and it just works. Definitely a fan as a USER of them. I'm sure people have their complaints as users and developers. But I definitely have to say it's been positive so far. Which is a rare consistency in the life of installing packages.