3 ms·
If you drop WSL then you get confused branding of what they are. WSL1 and WSL2 make it pretty clear you're getting the Hyper-V thing for the latter and the form
by sys_64738 6y ago
If you drop WSL then you get confused branding of what they are. WSL1 and WSL2 make it pretty clear you're getting the Hyper-V thing for the latter and the former is a Linux sys call API layer.
I'm actually surprised they can't be used together.
- javajosh 6y agoThose names don't imply anything about their implementation.
- hunter2_ 6y agoTangent: they imply running on Linux; a Wine substitute.
- archsurface 6y agoAgreed. Whatever the implementation the name indicates the next step in this solution. To do otherwise would be like naming windows95 something other than windows after windows3.1. Marketing.
- freeone3000 6y agoThere's a few exclusive portions, like the executable load error handler that triggers ELF to load under the subsystem, and the binding of the 'bash' executable. But mostly, to prevent a great deal of confusion.