5 ms·
I'll add the separate filesystems problem. I generally need to access files from both windows & linux. WSL 2 may have made file access faster within the vhd, bu
by crispinb 7y ago
I'll add the separate filesystems problem. I generally need to access files from both windows & linux. WSL 2 may have made file access faster within the vhd, but it seems to be slower to use those files from Windows, or impossible with tools that don't yet support the network file paths provided by the 9p server. VS Code's solution with the remote extension is really nice, but every Win tool would have to do something similar to make the experience truly seamless.
- nolok 7y agoFor the record I was used to SFTP NetDrive for my remote host (map a sftp target to a local drive on windows), and I just started using that to make sure all my windows tools can access it just fine. Doesn't solve the speed issue, but at least you're never blocked by a software that only work with a local/non-network path.
- crispinb 7y agoThat's a pretty nice idea for the net paths issue. I'll borrow it, thanks. I'd guess all significant Windows developer tools will add support for the wsl paths over time. VS Code obviously leads the pack with its remote extensions. I hope Jetbrains will do something similar with IntelliJ Idea - the piecemeal approach doesn't work as well IMO. I'll be interested to see what Microsoft can do about the speed of access to the windows file system. It's painfully slow right now.