Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good.
I don’t care if Firefox isn’t updated until I restart it. I just don’t want that terrible workflow:
Click update all. Firefox is open, therefore won’t update until you close it and click update again.
Every other package manager: Click update. All apps update. When I am ready to close Firefox it’ll be updated next time I use it.
Not really though? Or rather - then answer the other half. Why are flatpaks, deb, rpm, arch, etc. ALL able to update in place? But with snaps we need that sucker closed? It sucks to use like that.
Its also for my experience the worst way to use apps.
The fact that I can’t “update” my software without closing it first.
Why can I do that with all other package formats? I get it won’t be the new version until I reopen the app but still. Its unnecessary friction.
Also with the prompting last I used it Firefox couldn’t download anything with it enabled.
Like you ship Ubuntu with like 4 major snaps including the security center and it hasn’t or hadn’t worked with your shipped snaps for at least a year?
People using that distro gives me second hand embarrassment
Debian might work but it will always be behind and if any performance upgrades are done at a kernel level or a DE then you won’t get them until those fixes are potentially already obsolete.
You’re probably the first person ever to daily drive MX Linux, the most popular distro according to distrowatch