3 ms·
A while back spent about 2 mos mastering WSL2 and came to the conclusion that the default of automatically opening up in the Windows fs share was... unwise. Bes
by ncphil 6y ago
A while back spent about 2 mos mastering WSL2 and came to the conclusion that the default of automatically opening up in the Windows fs share was... unwise. Besides fs permissions being a complete mess, the unstable behavior described here liked to show up at the most inopportune moments. Wound up confining my work to the virtual Linux fs, but that kind of defeated the whole purpose of WSL for me. I'm also back to using a VMware machine on my company owned laptop, but my personal systems are still Linux on bare metal. As an aside, I struggled with Hyper V to replace VMware, but it makes the system unstable on the particular Win 10 builds my company provides employees. I'd gone at least 8 years not seeing a blue screen before that.
- sieabahlpark 6y agoI find wsl2 with docker to be a decent use case. You get a reliable terminal that doesn't just background processes you ctrl-c to. The IO is slow but overall manageable. File permissions are a joke but they're being ported into a container. I don't see WSL as an environment as much as it's just a more reliable terminal with a shotty emulated filesystem.