Introducing Surface Book 2

Re:Introducing Surface Book 2 by Viper007Bond on Tuesday October 17, 2017 @12:18PM (#15492188)

Windows Subsystem for Linux has been huge however. I used to have to run Vagrant or something on Windows to build stuff but WSL makes life super easy as a developer on Windows. I'm still one of the handful of people at a 600 person company though that runs Windows. :/

[ Parent | on HN ]

Re:Introducing Surface Book 2 by cube2222 on Tuesday October 17, 2017 @02:17PM (#15493306)

I'd like to second that. I've been using WSL + Docker on Windows for a long time now for web development (linux backend development) and it's been a breeze. Works flawlessly.

You can do fun things, like tail logs to a file using linux and simultaneously analyze the file using windows tools.

[ Parent | on HN ]

Re:Introducing Surface Book 2 by swah on Tuesday October 17, 2017 @02:26PM (#15493398)

How do you access your files inside the subsystem? Don't you get permission problems (executable files etc)? I had so many issues with Virtualbox in Windows, I rather just use a Linux desktop distro...

[ Parent | on HN ]

Re:Introducing Surface Book 2 by cube2222 on Tuesday October 17, 2017 @03:04PM (#15493819)

They made a compatibility layer.

You shouldn't access files in WSL using windows, but the other way around it's absolutely ok.

So if my projects are at C:/Development/Projects/...

Then I just open /mnt/c/Development/Projects/... on WSL

I haven't had any permission problems, not even once.

Same for Docker for Windows. It uses Hyper-V + some network disk sharing magic, which makes directory mounts into docker containers work great. So sometimes, like, when I need to debug a non-cross-platform linux program. (WSL doesn't handle process forking well, so some debuggers, like Go Delve don't work) I just do something like

docker run -v C:/Development/Projects/MyProject:/mnt/MyProject -it ubuntu /bin/bash

[ Parent | on HN ]