6 ms·
I also thought what you have described. However I have noticed that there are some advantages to WSL2. The biggest is that VS Code is so tightly integrated. It
by perryizgr8 5y ago
I also thought what you have described. However I have noticed that there are some advantages to WSL2. The biggest is that VS Code is so tightly integrated. It is truly plug and play. With virtual machines I had to constantly keep fiddling with ports and network interfaces and IP addresses. It really "just works" when you use VS Code with WSL2. Another is that Windows is smart about starting and stopping the Linux VM. I don't have to manage it. It starts up when you open a terminal or open your project in VS Code. It shuts down after some time if you don't use it. No memory usage, no CPU usage.
- TheRealDunkirk 5y agoThat's interesting. I've never tried it, but having it "just work" would indeed be nice, IF it always did the right thing. The first time it made a bad assumption that I had to tweak a config file to fix, I'd be running back to a "real" VM host. Have you ever had to do modify how it runs? (Maybe that's not even possible.)
- perryizgr8 5y ago> Have you ever had to do modify how it runs? No I haven't modified its behavior beyond a few of the common preferences in the settings page.