Yes, using Windows apps (beyond very simple things like the file manager) to deal with WSL resources, or vice-versa, is generally a bad time; WSL only really shines if you treat it like a separate computer, i.e. a Linux server you have access to. (This is exactly how VSCode's WSL extension does in fact operate.)

And yeah, if I had been given the choice, I definitely would have gone back to native Linux rather than stuck with Windows during the years I used WSL as my daily driver. But that would have been an uphill battle against IT that I wasn't interested in fighting, and I preferred WSL+Windows to MacOS. (Now that I've got an ARM Mac, the hardware advantage is sufficient that I probably wouldn't go back to WSL any time soon, but I still miss having a genuine Linux kernel without needing to run VirtualBox or something.)

[–] firelizzard 2 points 1 week ago

I have mixed feelings about macOS. I grew up using it and I talked my previous employer into getting me a mac for work but I’ve barely used my mac laptop in the last four years, even more so in the last year since I bought a Linux laptop.