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.
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.
Flatpaks are better than Snaps, but properly maintained dependency trees and SBOMs are best, by a wide margin.
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.
PopOS fucked me up with flatpaks
Gateway drug
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.
They are extremely effective at preventing PackageKit updates on my steam deck
plus that extra defense-in-depth layer of a sandbox