This looks interesting as a solution for Windows-only programs on Linux.
If I understand it correctly, it runs Windows programs inside a virtual machine container on Linux. The major difference seems to be that you don't get the virtual machine when you open a program, you just get the program window as if it were running directly under Linux. So, if that's the case, it would be pretty seamless, and it will use the Linux filesystem rather than having to sandbox everything, and all your files, inside the virtual machine.
That would eliminate most of my objections to virtual machines. You wouldn't have to constantly reconfigure it, you wouldn't have to figure out how to get that dinky VM window to full screen, and you wouldn't have to come up with workarounds to get the files you produce out of your virtual machine.
That would leave my virtual machines to be used just when I'm running questionable software, or visiting questionable websites, stuff that might bork my whole computer with a virus or trojan or something - I could just use them when I needed to test a new OS, or when I needed to sandbox programs or sites to keep my computer safe. I've used them a long time now for those situation. IF I brick a virtual machine, all I have to do is delete the container file and create a new one, rather than having to re-do my entire computer.
So, yeah, something worth checking into.
.
If I understand it correctly, it runs Windows programs inside a virtual machine container on Linux. The major difference seems to be that you don't get the virtual machine when you open a program, you just get the program window as if it were running directly under Linux. So, if that's the case, it would be pretty seamless, and it will use the Linux filesystem rather than having to sandbox everything, and all your files, inside the virtual machine.
That would eliminate most of my objections to virtual machines. You wouldn't have to constantly reconfigure it, you wouldn't have to figure out how to get that dinky VM window to full screen, and you wouldn't have to come up with workarounds to get the files you produce out of your virtual machine.
That would leave my virtual machines to be used just when I'm running questionable software, or visiting questionable websites, stuff that might bork my whole computer with a virus or trojan or something - I could just use them when I needed to test a new OS, or when I needed to sandbox programs or sites to keep my computer safe. I've used them a long time now for those situation. IF I brick a virtual machine, all I have to do is delete the container file and create a new one, rather than having to re-do my entire computer.
So, yeah, something worth checking into.
.
“Trouble rather the tiger in his lair than the sage among his books. For to you kingdoms and their armies are things mighty and enduring, but to him they are but toys of the moment, to be overturned with the flick of a finger.”
― Gordon R. Dickson, Tactics of Mistake
― Gordon R. Dickson, Tactics of Mistake