3 ms·
I'd love to use WSL2 but the longstanding issue with slow I/O between WSL <-> NTFS host is a dealbreaker. It basically means you have to keep all your data insi
by dirkg 5y ago
I'd love to use WSL2 but the longstanding issue with slow I/O between WSL <-> NTFS host is a dealbreaker. It basically means you have to keep all your data inside ext4 in Linux and that defeats the whole point - e.g. you can't keep your code, or files you download etc in Windows.
With WSL you can keep all data in NTFS, have near native speeds but you can't run a bunch of Linux cmdline tools.
I don't know if they can solve it, its basically sending data across the network, But this is the last barrier to a great Linux on Windows.
- waych 5y agoAh yes, 9p2000. The network filesystem where caching is non-existent and left as an after-thought.
- dboreham 5y agoI thought I'd have that problem but I just keep all my dev files in WSL2 now and I stopped using Intellij. VSCode has very fast WSL2 filesystem remoting.
- sz4kerto 5y agoTry IntelliJ Projector. It's awesome.
- phendrenad2 5y agoDoes it really defeat the point? I see WSL2 as a Linux VM with less hoops to jump through. Sharing data with the host system isn't useful, since I don't have programs on Windows that need to communicate with programs in Linux, and I store everything in github/gdrive anyway.
- the8472 5y agoMaybe go the other direction. Add an ext4 disk to the VM and then access it through \\WSL$\