The UI is not too complicated, which is why I like it. I use it to automatically unlock and mount my drives in /run/media/drive_name on boot.
I use Gnome Disks for this, even on Kinoite.
Yes
You can do this using Lutris.
Note that this isn’t a perfect sandbox. For example, the game can still send a link to your browser to open. Theoretically it could do something malicious with that. Though you could probably work around that issue by changing your default browser to a flatpak version and disable network access there. There might be other small sandbox breaks, but nothing I can think of.
I used to always remove Fedora Flatpaks, but I’ve grown to like them.
They are built from Fedora RPMs, so follow Fedora’s packaging and building guidelines. Meanwhile Flathub and snap are the wild west of packaging; many flatpaks/snaps are just repackagings of existing packages, which are often built against ancient glibc and libraries for broad compatibility for traditional packages.
They use libraries that are in Fedora’s repos. So any vendored dependencies in a Fedora Flatpak will get automatically updated once the app is rebuilt. Meanwhile on Flathub/snap, those vendored dependencies need to be manually updated (though there are tools/bots for Flathub that automatically check for updates and can even create merge requests). Upstream app developers may not upgrade their apps in a timely fashion.
I also much prefer how Fedora handles runtimes. I only have two Fedora runtimes on my system, Fedora Platform and Fedora KDE 6 Platform, which are both based on Fedora 41. Meanwhile on Flathub, I have 52 runtimes installed. Thankfully most of these are small, but there are still quite a few larges ones. Multiple versions of mesa, multiple versions of Qt, multiple versions of the Freedesktop runtime.
By far the biggest disadvantage is that they’re affected by Fedora’s copyright/patent restrictions. So most multimedia apps I end up installing from Flathub so I have working codecs. But there is some work being done that would allow Fedora Flatpaks utilize ffmpeg-full from Flathub.
Unless the OS installer chooses to wipe the driver, which Debian’s (non-calamares) installer does.
The virt-manager flatpak doesn’t work out of the box, you need to do some setup on the host. At that point you may as well use the deb of virt-manager.
It’s a year’s worth of improvements.
Though if you’re using Proton Experimental, you’ve already been receiving these improvements since it uses the staging (or git?) branch.
I believe Proton stable releases use the stable version of wine with fixes backported.