In this case the issue is with 100% on flatpaks side that they decide to ship and download the entire nvidia driver again instead of using the one of the host. Note both snap and appimage do not do this, they use the nvidia driver of the host.

There is no reason to have to download the entire nvidia driver again, distros cannot modify it as it is against its license.

Also even outside of nvidia you are still going to have troubles in games with flatpak if what you are using requires a recent version of mesa

.mozilla : “Oh but I AM special”

You would think that thunderbird would use ~/.mozilla as well but nope. It is ~/.thunderbird 🤣

Check my dotfiles https://github.com/Samueru-sama/dotfiles

0 hidden files, everything is in ~/Local.

Recently added this hack for ssh: https://github.com/Samueru-sama/dotfiles/commit/7e1f8bd3173da563731aea6db9efbf26a2b23e72

but Flatpak is good when you need sandboxes

flatpak sandbox is actually bad for web-browsers and electron apps:

https://librewolf.net/installation/linux/#security

https://seirdy.one/notes/2022/06/12/flatpak-and-web-browsers/

https://github.com/uazo/cromite/issues/1053#issuecomment-2191794660

appimage hasn’t depended on libfuse2 (or any libfuse) since the static runtime came out in 2022.

The issue is that some projects haven’t updated to it, most notably electron builder:

https://github.com/electron-userland/electron-builder/issues/8686

never integrate well on the system, and run unsandboxed.

https://github.com/ivan-hc/AM

You have sandboxing and perfect integration, including adding the binary to PATH.

flatpak still ends up using +4x times the storage equivalent of appimage, comparison with flatpak dedup checker for ~20 common GUI apps:

And btw I need to update this comparison, a lot of the appimages on the right got a lot smaller lately.

The flatpak runtimes are huge, the GNOME runtime alone is over 2 GiB so that’s +20 appimages.