I'm sure there's more specialized cases where it's not up to par, but for the average use case, it's quite good!
I'm sure there's more specialized cases where it's not up to par, but for the average use case, it's quite good!
Question: any issue with WSL2 and network connectivity to say services such as node running in your wsl2 that you would connect to from your browser? I’ve heard that in wsl2 there could be issues with this and you may have to do some workarounds or extra config magic..
Also, the WSL extension for VS code makes it hardly noticeable that you're even working in windows.
I believe there are some edge cases but you have to get into stuff that isn’t just “open a port and listen on it”.
You can mount the WSL2 file system in Windows, but then changes to files arnt communicated to apps. So your code editor wont know about changes made in the WSL2 env.
Not everything works or can with WSL2 either. There are some things you cant build and run.
I use Windows for games.
I also have a need for Adobe SW and MS Office. (requirment of my job).
macOS is great for dev, Adobe and Office. But I cant game on it...
There is no perfect OS for me right now. :-/
This killed me after switching from WSL1 to WSL2. I missed the part in the notes where it said you should no longer store your files outside WSL. Finally figured it out eventually and the speed improvement was huge.