Windows Feedback: a WSL love letter

Introduction

As many of you, you might have seen a request for Feedback from the Windows team and how it help us innovating, creating or simply help running our daily Business.

For me, while Windows 10 is certainly one of the best version so far, what really stood out since now almost 2 years is WSL.

So here is the text I sent as a feedback (minus the typos) and I will warn you: this IS a Love Letter. So if you're not interested in "Care Bear" writting, good bye and have a nice day.

The feedback

Windows 10 is for me the WSL love and the impact it’s causing on the “legacy IT genes” itself.

Since now ever, in a computerized view, Windows was the evil Dragon to be slain by the *nix knights in shiny armor.

And then Windows 10 came, with two main crazy ideas.
The first one is to have an unchanged, not recompiled linux environment running side by side with Windows and not virtually (as in Virtualization) separated.

And with the possibility to call binaries from both sides: Interoperability was born.

But *nix systems are more than technology, they’re a philosophy and that’s the second crazy idea which was actually triggered before Windows 10, and is now popularized during this era: be OpenSource.

So what is Windows 10 for me? a rebirth!

I fear no more going to conventions and say that I love Windows and at the same time use bash as my daily shell.

I’m no more looked at as I was an alien with a non-Mac laptop and not running Linux as my main OS.

Human change managment is hard and in a technological world, it’s even harder to be accepted (and it’s a “white bro” talking right...).

Windows 10, with such projects as WSL are showing that, if years of community divison made Microsoft “reign”, today by being inclusive, Microsoft is prospering and a respected Technology leader.

>>> Nunix Out <<<

Comments

Docker + WSL: Get 2 daemon for the price of 1

Introduction almost two years ago, Docker announced the capability of switching between the Linux and Windows containers "mode" (far from the right click that we have today). At that time, I wrote a blog post on how to run both daemons at the same time ( http://darthnunix.blogspot.ch/2016/10/docker-for-windows-2-daemons-enter-in.html ) Fast forward to 2018, and while we were blogging on how to get the TLS connection from WSL docker client with Rory McCune ( https://raesene.github.io/blog/2018/03/29/WSL-And-Docker/ ), another blog post, by Stefan Stranger drew my attention (read: blew my mind) as I was trying to reproduce the same: how could I "bind" the docker socket in WSL with the Docker for Windows Linux mode socket ( https://blogs.technet.microsoft.com/stefan_stranger/2018/04/02/access-my-docker-for-windows-kubernetes-cluster-from-debian-wsl/ ) From 1 to 2 daemon: DemonHunter mode achieved Now that we have all the required setup resources, let's b...

WSL: One Home to host them all

Introduction This blog post will explain how a single home mount can be shared accross all the WSL instances. It was quite fun to find the idea and then make it happen. It will use all the tools currently available from WSL, so please don't expect a "Linux only" as Interopability will be heavily used. And before I start, here is my point of view about WSL: It's not only Linux! It's different, just like GNU is different from Unix (yes I said it). We have finally the strength of both worlds combined. And while I do understand the "dev" aspect is meant to be reproducible in a Linux prod environment, the "ops" side is meant to take advantages of everything that can make the full environment feeling Home. Setup requirements In order to really enjoy this solution, I do recommend having 2 or more WSL distros installed or, if you fell like a real WSLCorsair, try @bketelsen crazy setup (I love it)! While the distros are downlo...

VSCode + WSL: the SSH way

The initial idea early 2017, Rich Turner made a demo where Visual Studio was used to develop C++ code, however the debugging environment targeted was WSL! With some magic, he showed something that he had forbidden from the initial release of WSL: writting directly to the WSL filesystem (still a big no-no actually). Of course, this triggered a lot of curiosity and the WSL Corsair had to loot from it too! SSH to save the day the biggest challenge was to find a way that not only could be easy to setup on both ends, and also would be approved by the WSL team. TLDR: if you use the Windows Path, You Die! #ThereBeDragons Another way, more Linux-oriented, needed to be used and hopefully a solution already existed and was simply waiting on being used: SSH🔐 The setup the setup is done in 2 distinct parts: Setup the SSH server on WSL Setup the SSH client on VSCode While the SSH server is a standard procedure in Linux, finding the right plugin for VSCode w...

Nunix Tech

Search This Blog