[abrookins]

That's okay -- I'm sure they fixed something like that issue! The WSL team has been crazy busy, and their work so far is super impressive.

VirtualBox shared folders had their own problems. `npm` wants to create symlinks for commands provided by packages, but VirtualBox doesn't support symlinks by default on Windows shares. So you have to execute an arcane command to enable that feature -- every time you restart the computer.

Interesting to hear that performance is decent with the Samba share. I presumed it would be otherwise. In that case, Hyper-V with Samba may be my last shot at getting the machine to work for me... we'll see if I can muster any more enthusiasm.

[Fnoord]

It is possible to create directory symlinks in Windows. It is called junctions [1]

[1] https://en.wikipedia.org/wiki/NTFS_junction_point

[gecko]

NTFS actually has support for proper symbolic links, which are not the same as junction points. I come across this confusion fairly often and I'm not clear why. (`mklink /d` is what you're looking for, and do note that this is different from `mklink /j` in meaningful ways. Do note these commands must be run from an Administrator shell prior to Windows 10.)

[EDIT: Also, reading GP, it looks like their issue is something about VirtualBox support for symlinks, not Windows support for symlinks. Symlinks are enabled in Windows by default, so they'd only have to do something special if they were on a domain that disabled them in the group policy--but in that case, they wouldn't be able to turn them back on themselves on a reboot anyway.]