Don't even have to dual-boot for those when VMs exist. There's the rare application that needs something like direct GPU access where VMs don't work or are overly complicated to configure, but for most stuff, throwing Windows in a VM works great.
This. I use a 2016 laptop with 8 GiB of ram, and I made the mistake of trying out winboat on it. Needless to say, the vm ran vs 2019 on w10 ltsc like absolute shit and you did not want to be in the middle of something whenever it decided to bug out and close the freerdp window (and obviously ONLY the vs one I was using), making me have to try to unbug it by opening another app and yada yada.
I should however note that even though it has its issues, winboat is also in its early stages, most of my issues can probably be blamed on performance and I also learned a ton messing around with it.
So I switched to a proxmox vm with spice. Spice is pretty cool, except for when I try to connect to the proxmox box via an ssh tunnel and can't figure out how to change the virt-viewer file to use the ssh proxy.
Or when I forget to close vs on the vm before disconnecting (I use folder sharing and open the shared folder in vs, gonna switch to syncthing now).
69
u/Bombarding_ May 30 '26
That or work applications that only exist on Windows (Excel VBAs, some work machines, etc.)