5 ms·
> I have high hopes for WSL2 replacing MacOS or Ubuntu VM's for me, especially because Darwin is simply not a linux system and you really feel the difference on
by hans1729 6y ago
> I have high hopes for WSL2 replacing MacOS or Ubuntu VM's for me, especially because Darwin is simply not a linux system and you really feel the difference once you work on natively compiled code.
That's exactly what I did two weeks ago, after years of working on macos I ditched it in favor of windows. I haven't looked back since. The native WSL-integration in windows' vscode is a blessing; you open vscode, it's already connected to wsl, you write your flask-app or whatever, and can access it from windows' chrome without intermediate steps. This setup feels leaps ahead of anything I've done on macos.
Bonus screenshot: https://i.imgur.com/7p5g5os.png https://i.imgur.com/7p5g5os.png
- qz2 6y agoWSL integration love wears off pretty quickly I find. There are so many rough edges and broken things. While debugging a UDP server recently I discovered that any attempt to capture anything via UDP was scuppered entirely by the networking abstraction. Also the bastardised lack of services is problematic. Thus I’ve gone back to virtual box and Debian. You still can use VSCode but have to jump through some more hoops
- shaklee3 6y agoAre you on wsl1 or 2?
- qz2 6y ago2 There are too many weird compromises and bugs with it. Better to stick with a tidier abstraction.
- anthonygd 6y agoPersonally the more I use WSL the less inclined I am to ever use either direct Linux or MacOS again. Of course, that's WSL 2, there are definitely rough edges on WSL 1.
- qz2 6y agoMy point was regarding WSL2. I will never use macOS again though. That is completely dead for me but that’s a whole another story.