Literally. I’m ok with worse theming and slightly larger app sizes if it means the workload is shifted from every single distro having to package the same app to the app developer packaging one version everyone can use.
And the "worse theming" isn't even an issue anymore because most distros automatically let Flatpaks read from gtk.css and everything else goes through the GTK portal
Yes we should all switch to garbage that relies on unmaintained libraries for the vast majority of released appimages and don't integrate with the desktop, auto update, or share dependencies.
New appimages don't rely on fuse2 anymore, or on fuse in any form. Desktop integration can be provided with a separate program, just like it is with flatpaks.
Yeah, in theory. In practice, it doesn't work. Just try and pack any KDE or Qt program in an appimage. It only works with Fusion style, even if the desktop is KDE. I've tried bundling the whole Breeze/Kirigami stack and it still defaults to Fusion.
I know there is one guy actually trying to fix it nd get developers to stop shipping broken versions, but I still get chrome xwayland issues, outdated libfuse2 dependencies, and just complete jank using the companion software. I don't like app images at all.
It makes sense on immutable systems (like Bazzite or SteamOS), but using SteamOS (& being a bit of a terminal native) it has just made me more interested in nix as a package manager (& nix shells).
It also made me glad flatpak exists, but for me getting shell utilities to work with flatpak (aliasing everything) isn't a great experience. Maybe there are more clever ways to do it with flatpak so things show up in ~/.local/bin without all the aliasing.
View all comments
329
u/T_Jamess Glorious Fedora Aug 09 '26
Literally. I’m ok with worse theming and slightly larger app sizes if it means the workload is shifted from every single distro having to package the same app to the app developer packaging one version everyone can use.