Every time I read this product name I think that the words come in the wrong order.
The Windows Subsystem for Linux is now open source
301–310 of 1001 posts
Re: The Windows Subsystem for Linux is now open source
#302Re: The Windows Subsystem for Linux is now open source
#303Earlier quoted context omitted.
Slow IO is why I still use wsl1.
I liked the networking in WSL1 more too
Corporate networking is why I still use WSL1 (I didn’t spend enough time to check why it doesn’t with WSL2, zScaler could be the culprit maybe).
However it’s not perfect, for example I hit this bug when trying to run node a few days ago https://github.com/microsoft/WSL/issues/8219#issuecomment-10... and I don’t think they’re fixing bugs in WSL1 anymore
Re: The Windows Subsystem for Linux is now open source
#304Every 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…
docker is pretty easy to use on linux (even rootless docker isn't particularly painful) and KVM using QEMU is also pretty easy for running Windows things. I used WSL quite a bit but ultimately have switched back to running Ubuntu as my main.
Here's the main difference between making Windows vs Linux the main OS from my POV: Windows is a lot of work and only the corporate editions can be converted into not-a-hot-mess-of-distractions (supposedly). Out of the box Linux doesn't have all of the bullshit that you have to spend time ripping out of Windows. You can easily re-install Linux to get the "powerwash" effect. But if you powerwash Windows you have to go back and undo all the default bullshit again.
Having said that Windows+WSL is a very nice lifeline if you're stuck in Windows-land. It's a much better combo than MacOS.
Re: The Windows Subsystem for Linux is now open source
#305Earlier quoted context omitted.
Yeah if you are working with Linux only, its better to go full linux. WSL2 is really handy when you want to run other software though. For example, I use Solidworks, so I need to run windows. Forscan for Ford vehicles also has to run under Windows. Having WSL2 means that I can just have one laptop and run any software that I want.
My development is mainly Windows and I prefer Linux host with Windows VM guests. The experience is more stable and I can revert to a snapshot when Windows or Microsoft product update brakes something or new test configuration does. It also allows to backup and retain multiple QA environments that are rarely used, like a client's Oracle DB. It is nice being able to save the VM state at the end of the week and shut it…
I too think it would be definitely more stable Linux Host with Win VM guests, but I can see the other way around being more convenient to get support for commercially. Though with the VMWare licensing changes, I think what is by default easier for commercial support options may be changing too.
Re: The Windows Subsystem for Linux is now open source
#306I 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.
Okay. Then you had a Mac. Then you need to run Linux in a VM anyway because similar to Windows, macOS is also a dumpster fire. Then why bother? You are going to have a Linux VM anyway. I usually just sync my VM disk between all my laptops & desktops, no matter what host OS it runs.
Re: The Windows Subsystem for Linux is now open source
#307Earlier quoted context omitted.
I find it to be incredibly janky. Pretty much every every time my computer sleeps (so every morning, at least) I have to restart it because somehow the VM-host networking gets screwed up and VS code connections into the VM stop working. You also can't just put things in your Windows User directory because the filesystem driver is so slow that git commands will take multiple seconds, so now you have two home directori…
> somehow the VM-host networking gets screwed up > extremely arcane things I had to fix when setting it up involving host DNS and VPN adapter priority not getting propagated into the VM so networking was completely broken Are you sure you set up the VPN properly? Messing around with Linux configs is a good way to end up with "somehow" bugs like that.
I don't know how it's set up. That's kind of my point though. I have to now be an expert in Linux and Windows to debug this stuff, which is a waste of my time as someone who's job it is to develop (server, i.e. Linux) software. I had exactly zero issues when I was using Fedora. At one point my company made all of the Linux users move off (we do now have an IT-supported Linux image, but I haven't found the time to re-set up my laptop and don't fully trust that it will work without a bunch of trouble/IT back-and-forth because they also made Windows users start using passkeys), and since then I've seen way more issues with Windows than Linux (e.g. one day my start menu just stopped reacting to me clicking on programs), in addition to things like ads in the lock screen and popups for some XBox pass thing that I had to turn off, which is just insane in a "professional" OS. A lot of days I end up having to hold down the power button to reboot because it just locks up entirely.
OSX was a bit janky with docker filesystem slowness, homebrew being the generally recommended package manager despite being awful (why do I sometimes tap a cask and sometimes pour a bottle? Don't tell me; I don't care. Just make it be "install". Also, don't take "install" as a cue to go update all of my other programs with incompatible versions without asking), annoying 1+ second animations that you can't turn off that make it so the only reasonable way to use your computer is to never maximize a window (with no tiling support of course), and completely broken external monitor support (text is completely illegible IIRC), but Windows takes jank to another level.
By contrast, I never encounter the issues people complain about on Linux. Bluetooth works fine. Wifi works fine. nVidia GPUs and games work fine. Containers are easy to use because they're natively part of the OS. I prefer Linux exactly because I stopped enjoying "tinkering" with my computer like 10 years ago, and I want it to just quietly work without drawing attention to itself (and because Windows 8 and the flat themes that followed were hideous and I was never going to downgrade to that from Windows 7).
Re: The Windows Subsystem for Linux is now open source
#308Earlier quoted context omitted.
I'm not saying it's a perfect solution, but with Windows 11 Pro and group policy I was able to disable all of the annoying stuff, and because it is group policy it has persisted through several years of updates. It is annoying you have to do this, and it does take some time to get set up right. But it's a solution. That said I'd pay for a dev edition as you described it, that would be fantastic.
There is no flavor of Windows 11 that is acceptable. Even the UI itself is a disaster. A cornucopia of libraries and paradigms from React Native to legacy APIs as if an interdimensional wave function of bad ideas had collapsed into an OS, but with ads.
[deleted]
Re: The Windows Subsystem for Linux is now open source
#309Earlier quoted context omitted.
"More powerful than Linux" is silly. It's a VM. The most useful thing is that it does a bunch of convenience features for you. I am not suggesting that it is not extremely convenient, but it's not somehow more powerful than just using Linux. You know what's even more convenient than a VM? Not needing a VM and still having the exact same functionality. And you don't need a bunch of janky wrapper scripts, there's more…
The integration between Windows and the WSL VM is far deeper than a typical VM hypervisor. You cannot claim with a straight face that Virtualbox is easier to use.
It's deeper but let's not overblow it.
I think the two fairly deep integrations are window's ability to navigate WSL's filesystem and wslg's fairly good ability to serve up guis.
The filesystem navigation is something that AFAIK can't easily be replicated. wslg, however, is something that other VMs have and can do. It's a bit of a pain, but doable.
What makes WSL nice is the fact that it feels pretty close to being a native terminal that can launch native application.
I do wish that WSL1 was taken further. My biggest grip with WSL is the fact that it is a VM and thus takes a large memory footprint. It'd be nice if the WSL1 approach panned out and we instead had a nice clean compatibility wrapper over winapi for linux applications.
Re: The Windows Subsystem for Linux is now open source
#310Every 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…
"More powerful than Linux" is silly. It's a VM. The most useful thing is that it does a bunch of convenience features for you. I am not suggesting that it is not extremely convenient, but it's not somehow more powerful than just using Linux. You know what's even more convenient than a VM? Not needing a VM and still having the exact same functionality. And you don't need a bunch of janky wrapper scripts, there's more…
The last time I deployed Linux servers on bare metal was about 2010.
Apparently Linux VMs on other people's computers is very much appreciated.