forget faster - functionally better. Firefox (at least in the past) used to break if you updated it while it was running (i.e. replaced / deleted / added files

forget faster - functionally better. Firefox (at least in the past) used to break if you updated it while it was running (i.e. replaced / deleted / added files its active runtime depended on). So you had to restart it. In a containerized world, this goes away. i.e. you can replace the firefox "image" with a new one that will be used next time you restart firefox without breaking the existant running one. with apt/deb you can't do that (besides waiting to update). On a multi user system (less prevelant these days for desktop use, but still existing) this can be really annoying to coordinate. This doesn't answer if Snap is the right technology to do it, just why apt/deb (and related tech) have issues that they can't really solve.