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

101–110 of 420 posts

Re: Windows Subsystem for Linux 2 Moving into General Availability

#101

Post by geerlingguy »

chx wrote: post #96
juped wrote: post #67

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

Well, if you want to use multimedia and do web development on the same machine, what are you going to do? Linux support is somewhere between nonexistent and utterly broken for the first one and the same can be said for the second on Windows. So your choices are, 1. run Linux primary, put Windows in a VM 2. run Windows primary and put Linux in a VM 3. Give up and just run a separate Linux server.

Or use macOS ;)

Re: Windows Subsystem for Linux 2 Moving into General Availability

#102

Post by Semaphor »

dboreham wrote: post #89
waheoo wrote: post #83

Earlier quoted context omitted.

The usecase was Apple has Terminal.app, Windows has MS-DOS. Tell me which you would rather use for node and or docker development.

Windows with git and its bash installed works surprisingly well for node development. Docker doesn't work on either MacOS nor Windows, right?

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

Re: Windows Subsystem for Linux 2 Moving into General Availability

#103

Post by kbutler »

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

I think of it as "Windows Subsystem for [running] Linux".

The architecture descends from the Windows NT architecture:

   The user mode layer of Windows NT is made up of the "Environment subsystems", which run applications written for many different types of operating systems, and the "Integral subsystem", which operates system-specific functions on behalf of environment subsystems.
Though as other users pointed out, in WSL 2, the name is inaccurate.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#104

Post by geerlingguy »

abhishekjha wrote: post #98
dboreham wrote: post #89

Earlier quoted context omitted.

Windows with git and its bash installed works surprisingly well for node development. Docker doesn't work on either MacOS nor Windows, right?

I have used docker on MacOS. I don’t know about windows but it ran fine on my mac. Is there something particular that didn’t work for you?

There are a number of use cases where Docker for Mac and Windows are painful compared to Linux, and to overcome those problems (like fs performance on shared volumes) people spend a lot of time building hacky solutions.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#105

Post by __d »

dboreham wrote: post #89
waheoo wrote: post #83

Earlier quoted context omitted.

The usecase was Apple has Terminal.app, Windows has MS-DOS. Tell me which you would rather use for node and or docker development.

Windows with git and its bash installed works surprisingly well for node development. Docker doesn't work on either MacOS nor Windows, right?

Docker runs just fine on macOS. eg. https://download.docker.com/mac/stable/Docker.dmg

Re: Windows Subsystem for Linux 2 Moving into General Availability

#106

Post by jacobr1 »

abhishekjha wrote: post #98
dboreham wrote: post #89

Earlier quoted context omitted.

Windows with git and its bash installed works surprisingly well for node development. Docker doesn't work on either MacOS nor Windows, right?

I have used docker on MacOS. I don’t know about windows but it ran fine on my mac. Is there something particular that didn’t work for you?

docker for osx uses a linux VM behind the scenes (transparently)

Re: Windows Subsystem for Linux 2 Moving into General Availability

#107

Post by MAGZine »

I recently wanted to run some linux apps on windows (simple stuff like ls, ssh-keygen, etc) and found that most instructions were actually pointing me to install a ubuntu VM rather than use the native subsystem stuff touted a couple years ago.

I was a little disappointed in this. Running a VM is a lot more hassle than just running the apps natively.

Feels like a step backwards than a step forward.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#108

Post by mcovalt »

_bxg1 wrote: post #77
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.

Font rendering is a bit blurry.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#109

Post by new_time »

geerlingguy wrote: post #101
chx wrote: post #96

Earlier quoted context omitted.

Well, if you want to use multimedia and do web development on the same machine, what are you going to do? Linux support is somewhere between nonexistent and utterly broken for the first one and the same can be said for the second on Windows. So your choices are, 1. run Linux primary, put Windows in a VM 2. run Windows primary and put Linux in a VM 3. Give up and just run a separate Linux server.

Or use macOS ;)

The devil on the shoulder has appeared

Re: Windows Subsystem for Linux 2 Moving into General Availability

#110

Post by Hello71 »

waheoo wrote: post #83
juped wrote: post #67

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

well, I definitely wouldn't use MS-DOS, because it doesn't support node or docker, but also because it's been obsolete since before Terminal.app existed.
Post reply on HN