The game development scenario feels to me like a case where a Windows based toolchain is going to be more coherent. I might be missing something though.
No, we don't/won't support a Linux port of our product at this time, and as a primary developer it's not worth my time to be hassled by it.
But WSL1 is _so nice_. I've fought with MSYS, MSYS2, Cygwin, various other bash environments and such, and I find none are quite as good as WSL1+X410.
And, let's be honest, if WSL2 is just another VM then it's a worse product than the other VMs that are available and far more mature. Hell, Canonical's Multipass is as good or better.
I really don't get why they went the VM route with WSL2. It seems to totally wipe out any advantage that WSL had over the other VM products.
I really don't get why they went the VM route with WSL2. It seems to totally wipe out any advantage that WSL had over the other VM products.
They're not deprecating WSL1 yet. You can still use it. https://docs.microsoft.com/en-us/windows/wsl/wsl2-faq#what-w...
But if you're looking for reasons, here are some officially stated ones. https://docs.microsoft.com/en-us/windows/wsl/wsl2-about
I/O performance and support for using Docker inside WSL seem like big ticket items. I'd agree with them that the trade-off of convenience sharing files between the two OSes for better support running Linux things in WSL is worth it.
