Windows Subsystem for Linux 2 Moving into General Availability

Post by ahupp » Wed, Apr 15, 2020, 5:45 AM UTC

AaronFriel wrote: post #140

In WSL1, running "wsl git status" on a moderately sized repo on an NTFS (Windows side) drive or SMB file share is nearly instantaneous. In WSL2, running the same command takes over 30 seconds. WSL2 is a massive hit to the seemless experience between the two operating systems with filesystem performance from Linux to Windows files orders of magnitude worse. Yes, unzipping tarballs or manipulating and stat syscalls are…

Post by saagarjha » Wed, Apr 15, 2020, 5:46 AM UTC

LeoPanthera wrote: post #158

chx wrote: post #152

Earlier quoted context omitted.

I will the moment you give me a mac with a seven row keyboard and a trackpoint.

Since you did not specify a laptop, you can plug in any arbitrary USB HID to desktop Mac. (MacBooks too - though I'm sure this isn't what you meant.) Most people choose their laptops based on the OS, not on the pointing device.

Post by dleslie » Wed, Apr 15, 2020, 5:48 AM UTC

AaronFriel wrote: post #173

dleslie wrote: post #171

Earlier quoted context omitted.

My git status/add/commit/push cycle has gone from seconds to minutes in length. It's unbearable and I'm going to abandon wsl as a result. Shame, it was really good.

You can convert WSL2 to WSL1! There's an argument to wsl.exe you can use to go back. Do it, free yourself (and your kernel)

Post by saagarjha » Wed, Apr 15, 2020, 5:50 AM UTC

souprock wrote: post #144

molticrystal wrote: post #13

VMWare [0] will also support the Hypervisor Platform Api [1] allowing it to run besides WSL2 which uses Hyper-V. VirtualBox is still struggling and runs slow if at all with WSL2 and Hyper-V [2] This of course has implications on how you setup Docker on a Windows machine, each way having pros and cons. [0] https://blogs.vmware.com/workstation/2020/01/vmware-workstat... [1] https://docs.microsoft.com/en-us/virtualizati…

This is a worrisome development. We seem to be heading toward a future where hypervisor drivers can only be provided by Microsoft, and you're out of luck if they don't do the job. Hypervisors that need more capability are going to have to do some crazy stuff to stay compatible. One option is to save and restore the whole hypervisor state whenever it runs. Another option is to be some sort of boot loader, seizing the…

Post by ahupp » Wed, Apr 15, 2020, 5:51 AM UTC

lostmsu wrote: post #114

nilkn wrote: post #41

Earlier quoted context omitted.

I never thought I’d say it but because of this exact setup with VS Code I’ve actually stopped using my MBP at home in favor of my desktop, which was really only built with gaming in mind. I’ve now gotten used to having all the extra computing power at hand and would struggle to go back to a laptop as my primary development machine.

But why could not you do the same before? Even before WSL there was MSYS, which IMO is great, unless you need to compile a C program, that directly uses Linux headers.