Does kind of feel that way. Having a full Windows Desktop with good graphics drivers and software like Microsoft Office, Photoshop, commercial games etc. and Linux for the programming/server-software side of things.
I have literally no reason to dual-boot with Ubuntu anymore. WSL2 and Visual Studio Code fulfils all my Linux coding requirements.
Maybe (probably?) a bad thing but it's damn convenient.
A Linux environment is superior for doing development (for everything I care about), and nowadays I've been able to play every game that doesn't have a native Linux port in Proton.
Be aware of the fact that WSL 1 and 2 can coexist. Running wsl -l -v from PowerShell should tell you which distribution is using which subsystem. You can change between the two.
If you're using WSL 2 and you put your Linux files on the Windows filesystem IO performance becomes spectacularly awful. If you keep your Linux files on the Linux filesystem it works rather well.
Docker should be installed on the Windows side with Docker Desktop and then associated with your Linux machines under Docker Desktop settings. This makes it available on both Windows and Linux. If you install it directly on Linux it only becomes available on that Linux installation and you get no interoperability.
Systemd tools will yell at you. I encountered issues when running systemctl. There are some fixes but I don't know if they work because I'm lazy so I worked around the issue instead.
I don't know if accessing the Linux files from Windows breaks them. I'm using VSCode remote extensions instead of mounting \\wsl$ and accessing it directly.
To some extent, yes. However, you will get the best performance (and improvement over WSL1) when working with files contained within the Linux file system.
