I switched to WSL2 a month ago and it's been great. With WSL1 I'd regularly run into subtle compatibility problems but haven't seen anything like that with 2. Despite a handful of annoyances, the Win10+WSL2+Visual Studio Code Dev environment has been a lot more pleasant than OSX.
Windows Subsystem for Linux 2 Moving into General Availability
81–90 of 420 posts
Re: Windows Subsystem for Linux 2 Moving into General Availability
#82> He further mentions that unzipping tarbars could see a 20 times performance increase. Boy, do I love unzipping tarbars! On a more serious note, it’s great that WSL has gotten much faster, although it’s a little disappointing that they threw out the older, more interesting architecture to get it and just used a VM.
The things I liked the most about WSL were the ability to share the same file system (and RAM, etc.) and not have to care about partitioning any resources. And to search the Linux files on the Windows side and even modify them with tools that can handle them (yes, I know what I'm doing). Now all of that goes out the window(s)... so I'm pretty unenthusiastic about WSL2. And the 9P server has been next to useless for m…
Re: Windows Subsystem for Linux 2 Moving into General Availability
#83I am giving up. WSL1 was a great invention but Microsoft gave up on it, either because of the filesystem performance problems or because of the debuggers. https://github.com/microsoft/WSL/issues/2028 (lldb, rr, delve all affected). This looks like a dreaded case of the first 90% is easy, it's the second 90% that is hard. Imagine implementing a translator for a vast majority of Linux syscalls just to find certain flav…
WSL was very cool from a pure tech standpoint, but I've never been clear what the actual use case for it was. WSL2 seems to be more along the lines of coLinux, which I felt the same way about when it was new.
Tell me which you would rather use for node and or docker development.
Re: Windows Subsystem for Linux 2 Moving into General Availability
#84As they are different there should be option to do both 1 and 2
Re: Windows Subsystem for Linux 2 Moving into General Availability
#85Re: Windows Subsystem for Linux 2 Moving into General Availability
#86Re: Windows Subsystem for Linux 2 Moving into General Availability
#87Out of curiosity, what do most people use this for? (I tried rewording this question a few times to not sound snarky, but failed.)
Re: Windows Subsystem for Linux 2 Moving into General Availability
#88Re: Windows Subsystem for Linux 2 Moving into General Availability
#89Earlier quoted context omitted.
WSL was very cool from a pure tech standpoint, but I've never been clear what the actual use case for it was. WSL2 seems to be more along the lines of coLinux, which I felt the same way about when it was new.
The usecase was Apple has Terminal.app, Windows has MS-DOS. Tell me which you would rather use for node and or docker development.
Re: Windows Subsystem for Linux 2 Moving into General Availability
#90On a Win10 host, I want to edit code in sublime and have the runtime environment in linux. I want fast code search and fast build times. I've found no way to accomplish the above. Code in Windows + Windows Sublime means build in WSL will be slow because cross-os i/o Code in Linux + Windows Sublime means code search will be slow because cross-os i/o Code in Linux + Linux Sublime + Winodws Xserver means interface is la…
What Electron-related problems have you had with VSCode? I've been using it as my primary for a few years now and it's been nothing but stellar. And that integration sounds incredibly cool.