3 ms·
I'm really torn with WSL. WSL1 has far superior performance when performing I/O tasks on the mounted Windows drives, but slower than WSL2 locally. WSL2 is unbea
by 91edec 6y ago
I'm really torn with WSL. WSL1 has far superior performance when performing I/O tasks on the mounted Windows drives, but slower than WSL2 locally. WSL2 is unbearably slow when performing I/O on the mounted Windows, using vim with a git pluggin or FZF is crippling. So I attempted to just use WSL2+vim on the linux local file system, but then when I try to run Windows npm scripts in a folder UNC paths cannot be understood by CMD.exe. It is the only thing preventing me from fully switching over.
- znpy 6y agoHave you considered switching to GNU/Linux instead? Given that you do all your work in a Linux environment already...
- nickjj 6y agoIf you have npm installed in WSL 2, what use cases are you running into where you need to run Windows npm scripts? You could exclusively run npm commands inside of WSL 2 and never have to touch cmd.exe.
- 91edec 6y agoI have to run npm scripts in Windows land because they launch electron apps that require Windows.
- spondyl 6y agoI agree with the sentiment around I/O which is the last remaining pain point. I only use it for Dropbox since my org files live there but I ended up installing the Dropbox CLI instead. It kinda sucks though since WSL 2 doesn't have a proper init setup meaning I have to manually start Dropbox's daemon anytime I restart
- stinos 6y agofolder UNC paths cannot be understood by CMD.exe Does using Powershell instead of CMD solve this for you perhaps (I mean, it does wrt UNC, but I don't know what else you're doing with it)?