I really wanted to like WSL 2 but it has a lot of bugs that may take years to get ironed out (unusably slow disk IO, memory leaks, virtual disks that grow forever, etc.)
I think it would probably work for web development as long as you keep everything inside WSL, but for other development tasks you're going to run into issues real quick.
I use WSL 2 for full time development on the stable release of Windows 10.
The last 2 issues are an issue as of today but you can workaround them where it becomes a non-issue in the end by setting 1 config file value and running 1 command maybe once a month.
Also if you keep your source code inside WSL 2's file system then the first 2 issues are non-issues in practice.
The last 2 issues are an issue as of today but you can workaround them where it becomes a non-issue in the end by setting 1 config file value and running 1 command maybe once a month.
Also if you keep your source code inside WSL 2's file system then the first 2 issues are non-issues in practice.