[compsciphd]

I'll take a counter approach. it makes sense to install firefox via snap.

firefox breaks if you overwrite its files. therefore installing "normall" via dpkg is bad while firefox is in use (especially on a multi user system). running via a container ensures that the existing running processes don't break while allowing you to upgrade and have any new instance get the new version.

there are reasons to dislike snap, but the usage of containers (even as simply a packaging mechanism, not any form of isolation) can improve user experience.

[antpls]

Same, I have been using snap to run Firefox and Chromium for about more than a year (personal usage, not professional), and rarely had issues. I had one issue regarding a feature like WebGL or a file picker, but it was solved after 5 minutes of googling, and it was about running a single command line to give more permissions to the snap package. This way of distribution works quite well for big applications with many dependencies that you want to be automatically updated without fear of breaking some shared libraries.

I also feels more confident trying new applications with snap. I know I can easily install different versions and uninstall them without breaking the system.