You might want to pay more attention to WSL2 then.
I'm a web developer who switched from Ubuntu to Windows earlier this year and WSL has very much been a "best of both worlds" solution. Continuous improvements to VS Code and Windows Terminal have made this transition very painless and WSL2 promises to eliminate most of my remaining pet peeves (e.g. improving Docker integration).
The only downside is that the filesystem is much slower but that's only a problem when compiling native software.
With WSL2, the filesystem is faster than 'native' windows (as long as you stay within the ext4-formatted image), which obviates one of the big Windows irritants for developers.
The one downside of WSL from my perspective is all the small impedance mismatches, wslpath hacks, etc that result from having to work with the two filesystems. And though VS Codes's remote extension makes working on WSL entirely seamless, the situation is messier with other tools. IntelliJ, for example, has some WSL support in individual plugins, but it's patchy enough that I found running the Linux version via an X server more convenient.
I'm a web developer who switched from Ubuntu to Windows earlier this year and WSL has very much been a "best of both worlds" solution. Continuous improvements to VS Code and Windows Terminal have made this transition very painless and WSL2 promises to eliminate most of my remaining pet peeves (e.g. improving Docker integration).
The only downside is that the filesystem is much slower but that's only a problem when compiling native software.