2 ms·
I mean, why not do that? I tried WSL because I thought it would be faster than a heavyweight VM. Turned out it's dog slow in comparison. Honestly don't see a
by pydry 6y ago
I mean, why not do that?
I tried WSL because I thought it would be faster than a heavyweight VM. Turned out it's dog slow in comparison.
Honestly don't see a use for it.
- shawnz 6y agoI find the opposite, WSL1 is much faster for pretty much every usage except workloads that involve reading/writing lots of files.
- pydry 6y agoThe difference on I/O is enough to make WSL unusable. I wasted a day trying to figure out if I had a problem with anti-virus or something that was blocking me before realizing that WSL I/O is just... well, slow. People kept telling me to upgrade to WSL2 to solve that but the version of windows I had didn't allow it. Might have been a blessing in disguise given the data corruption bugs.
- alexhutcheson 6y agoWhat version of Windows doesn’t have WSL2?
- shawnz 6y agoYou need at least Win 10 version 1903
- scpedicini 6y agoIt was introducing in windows 10 release 2004. A lot of users myself included are still stuck on the 1909 update because it does not show up in our list of automatic updates. This usually happens if Microsoft update determines that some of your hardware may cause BSODs with the new update.
- Koshkin 6y agoAny version from 1.0 to 10.1809.
- Dylan16807 6y agoWSL1 is much better integrated, which is useful for some things, especially when networking is involved. And it wastes less memory as a consequence. The root partition is slower, but I'm usually manipulating windows files anyway so both versions are similarly slow. I use WSL2 right now, but only because I need to mount a vhd that's formatted with BTRFS.
- birdyrooster 6y agoYou can’t compile anything with WSL1, did you notice that?
- Dylan16807 6y agoDo you mean kernel modules? You can compile programs just fine. There's a whole infrastructure around using visual studio code to run the UI natively and compile things inside the linux environment.