4 ms·
It's a horrible name that should never have been used externally, but it makes sense if you're familiar with the NT architecture. There's various environment s
by soneil 4y ago
It's a horrible name that should never have been used externally, but it makes sense if you're familiar with the NT architecture. There's various environment subsystems for win32, os/2, unix, and now linux.
If you look at the graphic at the top of https://en.wikipedia.org/wiki/Architecture_of_Windows_NT https://en.wikipedia.org/wiki/Architecture_of_Windows_NT it makes sense. But the fact that it needs this in order to make sense, is why it shouldn't have survived as a product name.
- ha8gda8gs11 4y agoThat's incorrect, they are not using any of the environment systems for WSL. WSL uses pico processes: https://learn.microsoft.com/en-us/archive/blogs/wsl/windows-subsystem-for-linux-overview https://learn.microsoft.com/en-us/archive/blogs/wsl/windows-... https://learn.microsoft.com/en-us/archive/blogs/wsl/pico-process-overview https://learn.microsoft.com/en-us/archive/blogs/wsl/pico-pro...
- anderspitman 4y agoThat's WSL1. This 1.0.0 announcement is about WSL2, which is based on Hyper-V VMs. As mentioned by others, the naming is quite confusing.
- ha8gda8gs11 4y agoCorrect, I should have been more clear. And to add to that -- WSL2 doesn't use any of the subsystems either.