Is it safer to disregard AppVMs completely by using named disposables for everything while storing everything in vaults?
Here’s my reasoning process:
—In AppVMs, /home files are persistent. If I make a named disposable then it becomes volatile(smaller attack surface even if I make a mistake(go to a suspicious link))
—Named disposable over regular disposables → Easier to distinguish between different qubes instead of a randomly generated number
—Named disposables won’t close even if you close the application that was used to open it. In plain disposable’s defense, startup times aren’t that big of a deal if you have preloaded disposables, but people might have this disabled. It’s also easier to lose progress with plain disposables
—The only 2 positives I can see is that you wouldn’t have to transfer files in & out of vaults if you were using a video editor in a disposable over an AppVM. The second benefit is that AppVMs saves your session cookies so you don’t have to login every time(maybe someone has an account subscription where they source stock videos from). If my use case is to only access cloud storage are there any risks with using an AppVM for this?
Maybe it doesn’t even matter because everyone’s use cases will be different(that there is no right answer)
Can anyone with experience in Qubes verify if my reasoning is flawed? Are there other huge benefits to using an AppVM over a named disposable that I’m overlooking?