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.
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.
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.
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.
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.
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
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.
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.
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
plus that extra defense-in-depth layer of a sandbox