[flukus]

> Parameters are passed to the Windows binary unmodified. As an example, the following commands will open C:\temp\foo.txt in notepad.exe:

This might rain on your parade a bit. Each island still has to know about the file sytem of the other island.

[0xFFC]

Cutting them some slack I think is not bad idea. They are literally integrating two big operating system together. Do you see what I am saying?

As we all know Microsoft messed up with mobile and web, but when it comes to software development they are ruler without even competition. Windows kernel is wonderful peace of software, and with this wsl they are literally showing industry how is software developed.

[flukus]

I will, they've been clear about it being a work in progress.

There are a lot of other people saying how amazing it is though, when functionality wise it's only just coming up to par with cygwin.

Edit - functionality wise as a usable bash shell, it's an acceptable linux virtual machine already.

[cheiVia0]

It is not a virtual machine and doesn't involve Linux in any way. It is an implementation of the Linux syscalls for the Windows kernel.

[flukus]

Why does this trigger so many people?

[cheiVia0]

https://www.xkcd.com/386/

[TazeTSchnitzel]

Why is “trigger” used jokingly now? Unless you think the people responding have PTSD or a similar condition.

[flukus]

Because self diagnosed PTSD sufferers on Tumblr made a mockery of it.

The word has uses outside of the PTSD context though, like gun or database triggers.

[tracker1]

I have to agree... I'm still using the bash that comes with git for windows. It actually works (mostly) as one would expect it to work.

Also, not being able to edit the WSL filesystem from inside a windows editor is a huge loss in terms of usage. It's worse than using Samba/CIFS to share a directory and edit across to a full VM. I happen to like my gui editor, but prefer to run in Linux.

[WorldMaker]

If you had to you can touch things in the WSL VolFS by browsing the appropriate %AppData% subfolder. I'm presuming Microsoft isn't encouraging that right now with this Interop tooling for several reasons.

At a guess one of them might be that apparently the Unix things like permissions and Unix-style metadata are stored in NTFS alternate streams (~"resource forks") that they may be worried some Windows programs might not handle quite right (ie, accidentally mangle/remove/destroy).

[tracker1]

It actually doesn't work right, and MS just closed the issue. I'd be fine with cifs automounts in the linux subsystem for windows file directories... I mean it may take a little work, but in the end, I want to edit files with a windows gui editor, and run them via the LSW applications. Until I can do that, it's an also ran on the desktop... and until it can be used for docker with linux containers on the server, it doesn't do much use there either.

[WorldMaker]

Why can't you keep the shared files that you want to GUI edit somewhere under /mnt/?/* in a normal NTFS folder? That works fine already today.

I'm using Bash on Ubuntu on Windows for Jekyll (because installing and keeping up to date Ruby on Windows is a terrible experience and this is a much nicer alternative). My files are in D:\Repos\..., I'll have VSCode open and Jekyll running in Bash in the equivalent /mnt/d/Repos/...