On Mon, 18 Dec 2023 10:17:34 +1300, I wrote:

When I first heard about WSL2, I predicted that Microsoft would, not from any conscious plan but simply from following the path of least resistance (and cost), start to rely on the Linux kernel more and more for important Windows functionality. I think this represents a step along that path.

Here <https://www.zdnet.com/article/windows-subsystem-for-linux-3-for-developers-sticking-with-microsoft/> is another major step along that path: the new version of WSL, i.e. WSL3, is getting even more of the bloat of Windows out from between the Linux kernel and the underlying hardware: Microsoft promised that WSL 3 will bring you "GPU and NPU without the performance tax." Under WSL 2, Microsoft added GPU support and improved graphics integration, but those features still operated through the VM. The resulting context-switching and translation overhead meant you had to deal with slowdowns when you needed GPUs and NPUs. That approach was OK for many developer workflows, but it seriously limited your performance when working with AI workloads, even if your PC came with dedicated NPUs. WSL 3 improves performance by implementing a new paravirtualized VM approach. Paravirtualization provides both a VM and access to the native hardware. According to Microsoft, "This means Linux containers will now run directly on Windows, with no additional configuration required." SJVN appreciates the irony of these attempts by Microsoft to get WSL closer to the performance of native Linux: Mind you, if you really want the best AI developer experience, you really should be running a Linux distro without Windows. However, if you're stuck with Windows, and many programmers are, thanks to out-of-date technology policies, WSL 3 will be a good alternative.