Though Entrop is right that it’s mostly just a power-user worry.
Not entirely. I’ve had a few snaps become useless when it comes down to providing configuration data. How an individual snap integrates into the filesystem depends on the author/packaging, and quality varies. Ultimately, it’s a PITA since the mapped filesystem paths are not in the stock/standard locations the product docs say they are. I chalk this up to packaging software that existed pre-Snap, or the original authors did not do the Snap packaging. It’ll probably get better as the ecosystem matures, but right now, it’s not a great experience unless the Snap-ed package can run as-is.
Not entirely. I’ve had a few snaps become useless when it comes down to providing configuration data. How an individual snap integrates into the filesystem depends on the author/packaging, and quality varies. Ultimately, it’s a PITA since the mapped filesystem paths are not in the stock/standard locations the product docs say they are. I chalk this up to packaging software that existed pre-Snap, or the original authors did not do the Snap packaging. It’ll probably get better as the ecosystem matures, but right now, it’s not a great experience unless the Snap-ed package can run as-is.