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.
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.
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.
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.
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.
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.
Both of these two cases are why Flatpaks are so attractive.
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 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 okay for stuff that doesn’t need deep access but they don’t work for many things.
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.
I’m going to be honest to you, I prefer appimages.
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
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.
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.
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.