Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Windows Subsystem for Linux 2 Moving into General Availability

infoq.com

Post reply on HN
Print view View original

71–80 of 420 posts

Re: Windows Subsystem for Linux 2 Moving into General Availability

#71

Post by veesahni »

On 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 laggy because, well, Xserver

VSCode gets around this by running in a client/server model with client on Windows and Server in Linux... but then I'm stuck with an Electron based editor instead of Sublime.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#72

Post by philliphaydon »

sk5t wrote: post #10

Is there a shell+terminal+font combo that folks really like for WSL? I've tried the new terminal beta with zsh and--for reasons I can't quite articulate right now--it feels "off" and I invariably proceed to boot up virtualbox for my debian, i3, kitty, fira code setup to get work done. Maybe it's the break in filesystems and $HOME? Edit: learning that WSL2 does away with the syscall-translating tech and mandates Hyper…

https://www.hanselman.com/blog/HowToMakeAPrettyPromptInWindo...

Been using terminal and 2 row powerline. It’s amazing. Hard to go back to conemu or similar in windows.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#73

Post by [deleted] »

chx wrote: 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…

[deleted]

Re: Windows Subsystem for Linux 2 Moving into General Availability

#74

Post by hu3 »

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…

Thanks. This information is important to me. I abbandoned WSL2 because it couldn't work along VMWare but the tide seems to have changed.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#75

Post by javagram »

rkagerer wrote: post #61

Am I the only one who thinks this was named backwards? Like, it should been: Linux Subsystem for Windows , or maybe Windows' Subsystem for Linux

It’s because “Windows Subsystem” is a thing. There was also a “Windows Subsystem” in the past that provided POSIX api’s and others.

https://docs.microsoft.com/en-us/cpp/build/reference/subsyst...

After WSL was dropped in favor of the VM approach in WSL2 it’s just a zombie name though I think?

Re: Windows Subsystem for Linux 2 Moving into General Availability

#77

Post by _bxg1 »

veesahni wrote: post #71

On 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.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#78

Post by simplicio »

aspaceman wrote: post #66
rkagerer wrote: post #61

Am I the only one who thinks this was named backwards? Like, it should been: Linux Subsystem for Windows , or maybe Windows' Subsystem for Linux

Totally agree. Feels like a “windows has to be first” type of thing.

There was a MS employee on twitter the other day (sorry, I forgot who) saying it was because there were legal issues with naming something with a title that has someone else's trademark as the first word.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#79

Post by chrismorgan »

rkagerer wrote: post #61

Am I the only one who thinks this was named backwards? Like, it should been: Linux Subsystem for Windows , or maybe Windows' Subsystem for Linux

People commonly say that, but with WSL 1 it was technically quite correct: it’s a Windows Subsystem, for providing Linux. Linux Subsystem for Windows would arguably be slightly inaccurate. The name just feels so strange because Windows hasn’t had many such Subsystems (win32 has essentially been the only one this century).

Under WSL2, the WSL name is no longer technically accurate at all, but it’s what everyone knows it as, and the difference normally doesn’t matter, so they keep it.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#80

Post by kyriakos »

eightysixfour wrote: post #6
jchw wrote: 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…

The integration is very impressive, latest builds even have access to the WSL2 file system from Windows. Starting up VS Code on a machine with WSL2 immediately gives you the option to use it as the VS Code environment, it is pretty great.

Integration is even tighter now its not just a VM like many commented here.
Post reply on HN