In case that wasn’t sarcasm: you probably don’t want to run your browser in this, since it already has a sandbox and you’ll have a measurable performance penalty by running in a virtual machine.
It wasn't sarcasm, although I don't know if it would become my daily driver either.
Performance is a non-issue for me, generally the browser performance is limited by pages waiting for ad networks to serve up ads. A pi-hole helps (and running in a VM/Sandbox lets you run the filtering DNS server as a local process pretty easily.
Lack of local data persistence is similarly a non-issue as the reason for running this way is to drop tracking cookies etc that fall out of a browsing session like leaves on an autumn day.
If it had some built in way to defeat the dozen other ways in which a browser can be fingerprinted, then it would be perfect.
Just a simple way to avoid the ad trackers and keep my actual stuff safe from the evil doers on the web.
The performance penalty for running your browser in a hardware assisted VM with a virtual GPU is much smaller than you may initial think. I do it regularly and doubt most people would even noticed if you didn't tell them to look for it.
"In case that wasn’t sarcasm: you probably don’t want to run your browser in this, since it already has a sandbox and you’ll have a measurable performance penalty by running in a virtual machine."
Actually, what I do want to do more than anything in this sphere is run browsers in a VM. The account containers in firefox is not enough.
This would work without performance penalty if you could chroot jail a gui application. There's almost no overhead in a jail - it's not a full blown VM, just a different chroot.
... but of course that's not a fit for OSX, which has no Xserver and blah blah quartz blah blah major spaghetti to get that working. Also OSX does not have 'jail'.
