I found a few small rough places trying to adopt it into my workflow, for example, in emacs if you type “-z” which you may do often in a bash script like "if [ -z … " the point just goes to the edge of the frame and then goes nuts if you keep trying to type. I have looked the WSL preferences to see if -z triggers some kind of hotkey, but if it does I can’t find it.
/tmp doesn’t get cleared after each reboot, which I discovered when I eventually ran out of space on my windows partition.
Also, the default distribution was ubuntu 14.04 when I tried it. Although apparently you can run do-release-upgrade on it.
All in all, I did not find a compelling reason to switch from Putty to remote into machines or a full VM when I want to run something locally. It sounds like Microsoft is putting effort into improving WSL, so I will try again in the future.
Edit: I forget about the one that took me a long time to figure out: There are also some weird interactions with git and MSVC. If you initialize a git repository in WSL on the mounted native partitions, if there are spaces in the file path, like there would be if your projects are stored in “C:\users\user\Documents\Visual Studio 2017 …” (which would so up in WSL as /mnt/c/users …") then either git fails to index or msvc fails to find its temporary project files which shows up as missing intellisense/compile command data.