5 ms·

WSL and VSCode have brought my machine pretty much to parity with developing on a macbook. I'm sure there's more specialized cases where it's not up to par, bu

WSL and VSCode have brought my machine pretty much to parity with developing on a macbook. 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!

indigodaddy 6y ago
I’ve got a new-to-me (used HP Elitedesk 800 G1 SFF with 16g ram/240g ssd and I5-4590 with win 10 pro for $150) arriving this week. I haven’t built or bought a PC (had a few MacBooks in between) in probably 15 years, so this puppy is going to be well good enough for me and I’m looking forward to having a proper PC and getting a nice WSL and terminal setup and Scoop etc.. 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..
- theaustinseven 6y ago
  I haven't had any trouble. I'm running an elixir project that I'm testing over localhost, and you don't have to do any port magic whatsoever. Just run the app in WSL and go to localhost:port in your browser. The only problem I've had is if you do any of your development in the windows part of the filesystem, you might run into weird file locking issues, but I haven't had many of those. Also, the WSL extension for VS code makes it hardly noticeable that you're even working in windows.
- munchbunny 6y ago
  I have a setup right now where I have the server (Flask inside a container) running on WSL2 and a browser in Windows pointed at it with no issues. 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”.
firecall 6y ago
The biggest issue for is that WSL2 is painfully slow accessing the local Windows file system. 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. :-/
- petitmiam 6y ago
  > The biggest issue for is that WSL2 is painfully slow accessing the local Windows file system. 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.
tomnipotent 6y ago
I just did the same yesterday and was pleasantly surprised how far things have come (it's been ~15 years since I've done anything but game on Windows). WSL (both 1 and 2) are both very polished, and configuring VS Code w/Remote WSL setup was very simple (Windows GUI + Linux dev environment). The hardest part for me was getting past the gut-wrenching fear of using Windows Store to install something, but the experience from Windows Store "Install" to Windows Terminal "Debian" shell was actually... enjoyable.

indigodaddy 6y ago

I’ve got a new-to-me (used HP Elitedesk 800 G1 SFF with 16g ram/240g ssd and I5-4590 with win 10 pro for $150) arriving this week. I haven’t built or bought a PC (had a few MacBooks in between) in probably 15 years, so this puppy is going to be well good enough for me and I’m looking forward to having a proper PC and getting a nice WSL and terminal setup and Scoop etc.. 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..

theaustinseven 6y ago
I haven't had any trouble. I'm running an elixir project that I'm testing over localhost, and you don't have to do any port magic whatsoever. Just run the app in WSL and go to localhost:port in your browser. The only problem I've had is if you do any of your development in the windows part of the filesystem, you might run into weird file locking issues, but I haven't had many of those. Also, the WSL extension for VS code makes it hardly noticeable that you're even working in windows.
munchbunny 6y ago
I have a setup right now where I have the server (Flask inside a container) running on WSL2 and a browser in Windows pointed at it with no issues. 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”.

firecall 6y ago

The biggest issue for is that WSL2 is painfully slow accessing the local Windows file system. 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. :-/

petitmiam 6y ago
> The biggest issue for is that WSL2 is painfully slow accessing the local Windows file system. 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.

tomnipotent 6y ago

I just did the same yesterday and was pleasantly surprised how far things have come (it's been ~15 years since I've done anything but game on Windows). WSL (both 1 and 2) are both very polished, and configuring VS Code w/Remote WSL setup was very simple (Windows GUI + Linux dev environment). The hardest part for me was getting past the gut-wrenching fear of using Windows Store to install something, but the experience from Windows Store "Install" to Windows Terminal "Debian" shell was actually... enjoyable.