The trick here is to not use any windows program to modify anything on the WSL file system (because of the unix permission system). But it works vice-versa ... so you can use any unix program to modify a file on the windows file system.
So my hack there is to simply make a symlink in my unix dir (`~/dev`, usually) that points to a folder on the windows file system ... that way I just do all my work in ~/dev and it's all good.
What’s the point then? Cygwin works better than this.
WSL works with unmodified Linux binaries, while you need to port/recompile everything for Cygwin.
I was simply communicating how to avoid this issue ... judgments of worth and value are a separate discussion.
Yeah - I generally touch files or create dirs in WSL first to get around it. Otherwise it is a cluster. If i could just use Linux @ work I'd be much happier.
Yes, you should have heeded the warnings against that. The article also mentions this in passing. You can get at Windows files from WSL, but don't do it the other way round.
you can get package managers on Windows as well, such as chocolatey or https://scoop.sh/
WSL is just a shitty implemention on a shitty OS. Linux and OS X work perfectly and they have package managers and I can control updates.