3 ms·
I don't think WSL1 was abandoned, was it? last I heard it was supported and meant to complement WSL2. I know of people who need WSL1 because WSL2 doesn't meet
by naikrovek 5y ago
I don't think WSL1 was abandoned, was it? last I heard it was supported and meant to complement WSL2. I know of people who need WSL1 because WSL2 doesn't meet their needs in some specific ways. so, yeah, if you know where that's documented I'd like to be able to show that to said colleagues.
- Hello71 5y agoin classic Microsoft fashion [0], WSL1 is not officially abandoned, but seems to be planned to be left in half-finished mode forever. bugs are closed as "fixed-in-wsl2" without further comment: https://github.com/microsoft/WSL/issues?q=label%3Afixed-in-wsl2 https://github.com/microsoft/WSL/issues?q=label%3Afixed-in-w..., including serious bugs causing incorrect computations: https://github.com/microsoft/WSL/issues/830 https://github.com/microsoft/WSL/issues/830. [0] see the dozens of official Windows GUI frameworks: https://news.ycombinator.com/item?id=16736720 https://news.ycombinator.com/item?id=16736720 (and since then, it's gotten worse: https://www.google.com/search?hl=en&q=uwp%20deprecated https://www.google.com/search?hl=en&q=uwp%20deprecated)
- Railsify 5y agoI'm hoping one day I can use wsl2 and virtualbox at the same time without suffering from cripplingly bad performance in vbox.
- minedwiz 5y agoSadly, that one seems to be on vbox. Windows exposes an API that lets a VMM like virtualbox create vCPUs on top of Hyper-V (https://docs.microsoft.com/en-us/virtualization/api/hypervisor-platform/hypervisor-platform https://docs.microsoft.com/en-us/virtualization/api/hypervis...). VMWare workstation and QEMU have added support for it and it works quite well, very close to native. I know vbox did implement it, but it seems to work not nearly as well. QEMU might work for your usecase though.