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.
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 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.
Both of these two cases are why Flatpaks are so attractive.
PopOS fucked me up with flatpaks
Gateway drug
Flatpaks are better than Snaps, but properly maintained dependency trees and SBOMs are best, by a wide margin.
Flatpaks are okay for stuff that doesn’t need deep access but they don’t work for many things.
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.
I’m going to be honest to you, I prefer appimages.
I respect your wrong opinion
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 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.