Live data from Hacker News

Windows Subsystem for Linux 2 Moving into General Availability

infoq.com

141–150 of 420 posts

Re: Windows Subsystem for Linux 2 Moving into General Availability

#141
post #53

Earlier quoted context omitted.

Stop blaming Hyper-V for "crippling other VM software". You ever tried to run VBox and KVM together? It's a limitation of the processor's virtualization extension.

Problem is once Hyper-V is installed and enabled, no other VM can even be started regardless of no Hyper-V VMs actually running. This limitation does not exist on linux afaik. I have run libvirt based VMs and VirtualBox VMs at the same time on linux just fine in the past.

Most likely you just wasn't using VirtualBox own virtualization since it's cant work alongside with KVM. Current version of virtualbox just use KVM just like libvirt.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#142
post #128
post #51

Earlier quoted context omitted.

They mean MS replacing the Windows kernel with Linux kernel. Which doesn't sound as crazy as it did just a couple of years ago. Just put all the Windows crap in a VM, similar to WSL2.

"Just put all the Windows crap in a VM" - if Windows such a crap why even mention it? Just put Linux on your PC and be happy.

There's a lot of Windows-only software out there that will exist regardless of how you feel about it.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#143

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…

Deactivating Windows Defender for the subsystem‘s storage folder helps somewhat, but I agree that the situation makes the WSL close to broken for many potential users.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#144

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 hypervisor capability before Windows can get to it.

That'll be some tough code to debug.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#145
post #129

Earlier quoted context omitted.

Did WSL1 not use the same binaries as a regular distro? IIRC it will download regular x86-64 .deb packages straight from e.g. Ubuntu’s APT repositories.

I think you read it backwards. It's cygwin that doesn't. WSL1 did.

Ah. My bad :) Should’ve known better than to comment here before I had my coffee.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#146
post #77

Earlier quoted context omitted.

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.

Font rendering is a bit blurry.

I haven't experienced this, but I mostly use it on a Mac. What OS are you on?

Re: Windows Subsystem for Linux 2 Moving into General Availability

#147
post #3

Earlier quoted context omitted.

I agree wholeheartedly. I know it was probably a fool’s errand especially in a world where Docker for Windows was doing the same thing WSL2 does but worse, but WSL1’s design just satisfied me in a way that Hyper-V will not. Presumably, this also means you have to have Hyper-V enabled, crippling all other VM software. Hope the integration is impressive at least, to hopefully make up for it. I admittedly don’t run Wind…

> Presumably, this also means you have to have Hyper-V enabled, crippling all other VM software. This is being addressed, as discussed by commenter below [1] and at [2]. [1] https://news.ycombinator.com/item?id=22874047 [2] https://blogs.vmware.com/workstation/2020/01/vmware-workstat...

Great to hear. I suppose this means I should consider keeping my Workstation license up to date...

Re: Windows Subsystem for Linux 2 Moving into General Availability

#148

Earlier quoted context omitted.

Windows has direct docker support and has had it for a while. Not sure how great, not into containers myself ;)

Just like on Mac OS it runs in a VM.

soon it won't (at least, not on its own- in the wsl2 VM) https://www.docker.com/blog/new-docker-desktop-wsl2-backend/

Re: Windows Subsystem for Linux 2 Moving into General Availability

#149

Earlier quoted context omitted.

Windows has Windows Terminal and PowerShell, too. Apple and Linux also have PowerShell.

Presumably the draw is UNIX, not the Terminal app itself.

One of my main pain points in Windows is that the terminal app options are so crap compared to iterm2 or even the plain terminal app. The app itself is definitely a draw too

Re: Windows Subsystem for Linux 2 Moving into General Availability

#150
post #59

I 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…

I haven't used all variants of VMs but my experience with VMs is very different from WSL2. For example: * Smooth set up. Don't have to install some large commercial 800MB MSI like VMware workstation, download some Linux image, go through partitioning of file system etc. * Well integrated. I can open up a terminal and it acts as any other window in my system (meaning I don't get the window in a window effect as you ge…

I have been using multipass very successfully the past few weeks. It's a full fat VM and has an experience very similar to that of WSL. https://multipass.run/
Post reply on HN