back
1194 comments
When WSL came out I was absolutely overjoyed - finally an actual linux shell on windows! I use windows for my gaming pc, and I wanted to have a unified gaming/dev box. It felt like the solution.

Over time though more and more small issues with it came up. Packages working not quite right, issues with the barriers between the two, etc. It always felt like there was a little bit more friction with the process.

With Valve really pushing Proton and the state of linux gaming, I've recently swapped over to Ubuntu and Nixos. The friction point moved to the gaming side, but things mostly just work.

Things on linux are rapidly getting better, and having things just work on the development side has been a breath of fresh air. I now feel that it's a better experience than windows w/ WSL, despite some AAA titles not working on linux.

WSL 1 was supposed to be like "Windows on NT" where it emulated the Linux kernal to the NT one. they skipped a ton of features then dumped the whole thing for a containerized virtual machine thing for version 2. Wish the NT one worked out but I get it being complicated.
I had the same experience. Even installing linux is easier for me now. And with new spyware features of windows, there is really no incentive to use it
I truly believe if AAA titles would not release for windows exclusively no-one would have a good reason to use windows really besides inertia.
I was excited about it too, even just having a tmux and using it for grepping and file copying. Then after a year or two on windows, my computer started slowing down. Tale as old as time. I'm not surprised, and some of the issues aren't ms' fault, but nevertheless I see CPU spikes to 100 with several browser tabs open, or the drawing tablet driver goes to 100% cpu usage even though I never even use it. The UX shouldn't degrade like a mechanical system.
Curious, if you don't mind answering, do you mainly uses Ubuntu or Nixos, and which one do you liked more ATM?

Regarding Steam, do you install it with distro provided or through Flatpak?

What is the spec of your machine that you do Linux gaming on? I've noticed a notable performance penalty (around 10%, even higher on GPU heavy games) when running games with Proton, which is mainly why I haven't dropped Windows yet.

I think actually Linux has come a long way and recently I actually dual booted fedora with windows and fedora was easily my main choice unless gaming.. unfortunately when updating from 41 to 42 there was clearly an issue with the GPU not having drivers for acceleration or cuda, updating the drivers bricked the OS immediately and while I could recover, I spent hours and hours on this and could never get the GPU drivers installed again without bricking it.. ultimately I realised how at mercy of drivers Linux is. I hope though that in the next few years things improve as windows is dismal to work on these days
Just curious, which games gave you problems?
i think everyone tried that. gpu (games etc) are the only thing holding windows relevant at this point.

i have some 2012 projects were the makefiles also build in msvc. never again.

then 2015 projects with build paths for cygwin. never again.

then some 2019 projects with build scripts making choices to work on msys2/git-bash-for-windows. never again.

now we can build on WSL with just some small changes to an env file because we run a psql container in a different way under wsl... let's see how long we endure until saying never again.

Why would anyone run malwares on purpose on the same machine they use to do development/work?
I would do it the other way round: use Windows in a virtual machine from Linux. If you are in Windows and have the urge to use Linux, do the proper switch once and for all. You will never look back. I haven't in almost 15 years.

Given what Windows has become and already discussed here on HN I would even hesitate to run it in a virtual machine.

Edit: more than 15 years.

WSL 2 is one of the biggest reasons I'm able to be productive as a blind software developer. With it I'm able to enjoy the best desktop screen reader accessibility (Windows and NVDA) as well as the best developer tools (Linux). I hate Microsoft's AI and ads force-feeding as much as anyone else but trust me, you'd do the same if you were in my shoes. Screen reader accessibility on Mac Os is stagnating even faster than the os itself and even though Linux / Gnome accessibility is being worked on, it's still ready only for enthusiasts who don't mind their systems being in a constant state of somewhat broken, as illustrated by this series of blog posts from just a few weeks ago: https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-d...
I've been using WSL on and off for Linux development for the last few years.

When it works, it's great! When it doesn't....oh man it sucks. It has been non-stop networking and VPN problems, XServer issues, window scaling issues, hardware accelerated graphics not working, etc. this whole time. I've spent more time trying to fix WSL issues then actually developing software. It's never gotten better.

It's fast. It's powerful. But using it as a daily driver is very painful in my experience. I avoid it as much as possible and do most of my work in MSYS2 instead. Sure, it's much slower. But at least it works consistently and has for years.

Every time I praise WSL on hn I pay the karma tax but I will die on this hill. WSL is more powerful than Linux because of how easy it is to run multiple OS on the same computer simultaneously. It's as powerful as Linux with some janky custom local docker wrappers for device support, local storage mapping, and network mapping. Except it's not janky at all. It's an absolute delight to use, out of the box, on a desktop or laptop, with no configuration required.

Edit: for clarity, by "multiple OS" I mean multiple Linux versions. Like if one project has a dependency on Ubuntu22 and another is easier with Ubuntu24. You don't have to stress "do I update my OS?"

Given the layoffs round from last week, in a record earnings year, I wonder if this is a side effect of those layoffs.
Note that this doesn't include lxcore.sys, the kernel side driver that powers WSL 1.

(Also, I'm surprised that WSL 1 is still supported. It must be in maintenance mode though, right?)

WSL is a landmine of bad design. I lost all my data once, and that incident made me switch to a Mac.

Here's how you can lose all your data - and Microsoft engineers won’t care: https://github.com/microsoft/WSL/issues/8992 https://github.com/microsoft/WSL/issues/9830 https://github.com/microsoft/WSL/issues/9049#issuecomment-26...

I still can't believe how people use windows as their main system with all the extremely invasive telemetry and bogus "AI" features that hogs a LOT of resources at idle
Not a Windows user, but I think WSL is great. I see a lot of Windows user criticising Linux for... essentially not looking like Windows. "Linux Desktop will never reach mass adoption unless it [something that boils down to 'looks more like Windows']".

The thing is: I consider myself a real Linux user, and I don't want it to look like Windows. And I hate it when Windows people try to push Linux there, just because they want a free-with-no-ads version of Windows.

In that sense, if WSL can keep Windows users on Windows such that they don't come and bother me on Linux, I'm happy :-).

People just want to bash Windows left n right. But no other OS in history has been this mature with handling GUI snd and providing the flexibility, customisations etc.

Before I say anything, Windows 11 is bad.

I remember playing with Win98, XP , I would modify many many registry settings, mod binary files to do something with games, you could access all sorts of weird hardware which only had drivers for windows!

Windows 98-7 were best for learning stuff about computers (inner workings etc).

I remember, to remove viruses (XP)I was trying to hard delete system 32 folder, it deleted lots of files and it continued to run!

meanwhile Apple won't even make it easy to boot Asahi Linux on Apple Silicon.
I would love if the bug(s) with working on the windows filesystem from within wsl could now be fixed. https://github.com/microsoft/WSL/discussions/9412#discussion...
>Lxcore.sys, the kernel side driver that powers WSL 1

This isn't open source, and considering that this is probably what ties into/sets up WSL as a windows subsystem that's a bit of a bummer.

The rest is just a Virtual Machine for the most part, isn't it?

WSL is amazing. Nothing short of it. My laptop SSD controller died on a conference. I bought a 200 dollar netbook running windows, installed WSL, downloaded the MDADM packages, was about to mount the encrypted drive with cryptsetup, mount the ext4 partition, then chroot into it, then my home drive was like working on my old laptop.

I did this in about 20 minutes, with the help of chatgpt.

In the end I was able to keep working through the trip and provide some demos to clients which landed us some big deals.

Go WSL!

WSL is a stupid idea. Microsoft should just stop developing and maintaining its windows kernel and built a windows compatibility layer on top of Linux.
Wow. In 2009, when it looked like Microsoft was the most closed company of all time, I was telling people at work, they should port windows to the linux kernel. What happened over the next 15 years, I don't think people would have believed it if you told them back then. Things have changed.. ALOT. Now granted, this isn't what I said they should do, but you know, eventually they might see the light.
I'm not be sarcastic or funny when I ask this. Why isn't this called the Linux subsystem for Windows? It seems like a Linux subsystem running on Windows. If it were the other way around, (ie, a Windows Subsystem for Linux) I'd think that Linux would be the primary OS, and something like WINE would the subsystem.
WSL1 got my hopes up that we were on the path to Windows supporting the Linux user space API but then it was cancelled and replaced with a virtual machine based solution that I didn't need WSL2 to implement myself (with more flexability and capabilities).

I'd much prefer a proper compatibility layer that converts Linux system calls to their equivilent Windows calls and those calls be exposed from the Windows kernel itself.

That way I could just run Linux applications, bash, zsh and development tools directly on top of Windows without needing any "remote development tools" in my IDE or whatever.

Something closer to MSYS2/git bash/busybox for win - but where tools can ignore their Windows specific stuff like the filepath seperator.

It's fine I guess

Not only open source, but extremely well documented.
WSL1 is the good one, WSL2 just runs Linux simultaneously alongside Windows.
Nice but where is the code? Is it just very, very incomplete or a joke?
Not sure about the impact of WSL because personally did not use it but I do know couple of friends who stopped spinning up Kali VM because of WSL.
M$ contributing to open source is great, but I switch to Linux because I don't trust Windows, the OS. Not because of accessibility.
I never even realized that it was tivo-ized. Probably because I haven't been on windows since before WSL became a thing.
I have to use Windows as my main box after nearly 6 years of MacOS (and before that Mint) and WSL2 helps me keep my sanity.
WSL is the main reason I switched from Mac/Linux to Windows two years ago. Excited to see this move!
Does this mean Microsoft is abandoning it as end of life? It's hard to tell intent here.
WSL1 was hobbled by needing to calculate Unix Permission numbers and hardlink counts for every file. On Windows, you need to create a handle to the file to get those things. That's a file open on every file whenever you list a directory.
Every time I read this product name I think that the words come in the wrong order.
The title is misleading and ambiguous as to whether this applies to WSL1 or WSL2.
Maybe someone will finally build my dream: a WSL distro that I can also dual-boot natively. I'd love to switch between bare-metal Windows with WSL and bare-metal Linux with virtualized Windows at my leisure!
WSL is amazing if you work for a non tech company that is a windows house but want to do development in Linux. It’s seamless (at least to my middle ability) for VS Code.
Sec guy (who was mainly a linux guy) was never happy to let people use WSL in corp due to security bugs.

Can anyone chime in - is this still a concern? Was it ever a concern?

WSL is ok, I can run drop down terminal quickly to run any command and VS Code is well integrated with it. Too bad it's very slow.
I wonder if this is in any way connected to devcontainer becoming more prominent in Github and VSCode?
Why isn't it "Linux Subsystem for Windows" as it is a Linux subsystem running on a Windows os?
Can I use a vanilla kernel with it yet?
WSL going open source is a huge win for devs. Can’t wait to see what the community builds with it!
Cool! This means I can fix mDNS now!