WSL3 Performance is about 5-60% faster than WSL2 depending on the workload
tonym.us
tonym.us
Another big thing is getting lookingglass working. I could not for the life of me figure out what I was doing wrong when I followed the setup guide 1 line at a time, but AI figured out the problem and it it working in 1 hour. And yes it took AI one hour to figure it out so you can assume how long I've sent trying to get this to work.
Now I run a custom kernel with custom KDE and several compiled new packages which would require the effort of a small team, but now it's possible to do with few prompts and it's relatively easy to maintain indefinitely.
Also AI got me off jetbrains onto nvim and I haven't been this happy writing code.
But now, I just open Claude Code and say "this is bothering me" and it runs in the background while I complete other tasks. I get it to document anything it changes and push my custom configs into a private git repo along with my dot files.
In some sense, I'm starting to see Linux almost like a Smalltalk image. Anything permanent is backed up to git and I have documented recipes to go from fresh-install to custom environment in a couple of hours.
There are still a lot of rough edges all over the place but it is a totally workable environment.
I'm waiting to see if Omarchy switches to NixOS for their next major release. I have ~100GB of unpartitioned space ready for experimentation and NixOS is the most likely candidate.
Plus I went and installed a bunch of cool desktop effects so it's cool to me now :)
A recent update crashed in the middle and left me running an incorrect kernel for my GPU drivers, if I had of rebooted I'd have been hosed. Thankfully Claude caught it before that happened (steam games refused to run) and fixed me up.
In related news - not a fan of flat pack.
So, yeah, I feel that pain. So far I've been careful and/or lucky.
But everyone knows that performance of WSL is nowhere near native linux on the same machine.
The shell grows not old, as we that are left grow old:
Aix shall not weary them, nor the years condemn.
At the going down of Sun and in the morning
We will remember them.
Maybe those are interesting as teenager hobbies as well.
Recently I needed a certain agent to help me automate some Excel stuff. Getting it to work in Windows was significantly harder if not impossible compared to WSL.
We are not talking about a properly configured Windows workstation. We are talking about corporate PCs configured by an IT department that is completely oblivious to the needs of developers, most likely because developers are not their bosses. WSL is effectively an escape hatch.
Usually the stated reason is "security", and developers tend to do the greatest sin of corporate security: they run arbitrary code, and they even have the nerve to call it "their job"!
I don't work in corp IT, but I am convinced that people there are not stupid and they are fully aware of the "shadow IT" aspect of WSL, but they give it a pass because they are also aware that people have "real work" to do that would be impossible otherwise, given company policies.
No, not stupid, per se. I generally don't like to blame people for the situations in which they find themselves. But there is something else going on.
I find the folks in such IT departments are generally not very good at their jobs. One potential reading of this is that it is not the people working in the jobs' fault, it's the design of the corporate leadership by not paying well enough for the job to get better people.
But the knock-on effect would be, if corporate paid better, at least my IT department would look completely different. The people we have now would be replaced by much more competent people. These more competent people would also generally be folks who shower and wear clothes that fit, that they don't let one corner of their shirts hang out the waist of their pants, that didn't show up to a service call wreaking of cigarette smoke. I'm not expecting people to spend more money on nicer clothes, I already established they don't have that money. I am expecting people to take care of their basic hygiene and present themselves as best they can. That they don't is a signal they don't really care about their own professional development. If corporate paid better, IT wouldn't be staffed by a bunch of literal slobs.
Though they are in a bad situation, I don't have a lot of respect for the folks in my IT department, because the only job they have, the one they have been sticking to for some time, they are only doing the bare minimum. I've been poor. I've been in jobs I hated. The only way out was to suck it up, present myself well, get better at my job, and go somewhere better. I have a hard time respecting anyone who just gives up.
(To be fair, there actually are a few who do appear to be doing this, but they are few and far between. They also don't last long, because again, they go on to something better. I'm talking about the kind of people who don't put in the effort and then complain they never get anywhere.)
Because their job is keeping their job, not making the 50 developers in the 5000 person org happy, as those are not their bosses.
You judge their competency from the perspective of a dev in the trenches, but the way management judges their performance is vastly different: keeping IT cost center spending as low as possible(hence a lot of IT offshoring) and security as tight as possible (hence MFA, EDMs and MDMs shoved everywhere that don't led you run anything besides notepad and Edge). Whether this hampers the devs or not is irrelevant for them or for management (outside of purely tech companies) since this is the devs' problem to deal with, not IT's problem. The moral is as long as it's seen as a cost center and not a profit center, there will never be right incentives to have a competent IT department staffed by competent people.
And keep in mind that a lot of the hidden champion engineering companies that make the world go round still function on excel sheets with VBA scripts as their "tech stack", and as long as that runs, management is happy. If you tell them you want to run linux, python, node, docker on your notebook, they'll probably laugh in your face thinking it's some hacker alien gobbledygook.
I definitely agree with that part though I've not used Windows at home for many, many years...and I'm a gamer.
Other than that, I believe the productivity tooling is better on Windows.
I myself fall in the SaaS category, so Windows doesn't give me anything. On the contrary for whatever reason after mainly using Linux/OSX for 15 years, Windows just feels clunky and like it "gets in the way". WSL is a good hack/workaround, but unless I MUST have Windows as OS (because of a work provided Laptop that cannot be Linux), i dont see a point of using WSL.
Luckily my IT staff allowed me to dual boot windows and debian+cinnamon. Everything was going great until I needed to compile and test a legacy firmware using Keil uVision... Gonna be on windows a while longer unfortunately :(
This doesn't make any sense. I regularly use Windows for a few things, and do not have this problem. Sane corp group policies disable all the annoying things folks complain about on the default consumer install, and there are few things you can't do just using a keyboard and keybindings.
I still prefer Linux and KDE is my daily driver but most of the comments I read here about Windows seem to be people regurgitating second-hand comments they read and passing them off as their own, and it's always the same small list of things every time.
> fighting against the annoyances
Because they're trivial annoyances. I spend just as much time disabling or changing annoying things on KDE (or MacOS), I don't see the difference other than "Microsoft bad!" At the end of the day the same amount of my time is wasted. I'll save my moral outrage for actually important things.
Linux to me feels like it's designed for multi-user systems and servers, where I use it as a single person to launch software.
A lot of stuff in WSL 2 is often faster than doing it natively on Windows as a result.
Sadly the rest of Windows 11 suffers from those unasked, opt-out feature drops. Unbearable. So, I'll go pure Linux again.
I still use Win10 for a few things, including testing stuff works there too, via java. I switched to Linux in 2004 or so, though.
In current WSL2, Windows owns the IP address, the NIC, DHCP, ARP, etc, and it’s shared with the Linux VM.
It’s really kinda magic… Linux sees the same IP address as windows does, and you actually get address-in-use errors if Linux tries to listen on a port Windows is already listening on, and vice-versa. So there’s no NAT going on or any internal 172.x net within the Linux VM, you just run “ip addr show” and you see the same real IP addresses that “ipconfig” shows you in windows.
(I no longer have a windows installation but WSL2 got noticeably better with networking some time before I gave up on windows.)
I'm a hardcore Linux user, but it's a fact of life that laptops are not very well supported. There are some that are very compatible, but generally speaking, I need to trade off software (Linux compatibility) for hardware (laptop choice) or viceversa.
WSL allowed me to choose any laptop I want and run the subset of Linux that matters for me. For my use case (that is, not quickly accessing huge amounts of files, performance was ok - as a matter of fact, the author of the article got a very reasonable performance loss on realworld tasks (-4% ~ -16%).
The only thing that I found truly irritating is attaching USB storages, but I ended living with that.
Remember, Halloween documents' opening salvo was the idea of extending ACPI so that Linux becomes unbootable on PC hardware.
Hibernation is the same deal. You also need to have a swap file/partition slightly larger than your RAM, since it's dumped to SWAP during hibernation.
So, why don't you come over here? We have cookies.
My last machine, according to reviewers, worked "well" on Linux. After I purchased it, I've found that the battery lasts half of what it lasts in Windows. And other stuff.
No doubt that there are 100% compatible machines (Thinkpads, typically), but again, it limits choice.
No, that isn't a fact at all. I use Dell laptops and have run Desktop Linux on them (Ubuntu past years and more recent switched to Kubuntu) and all of the hardware has worked well, even for gaming, even for my laptop with nVidia built in.
Haven't regretted it for a second.
Given raw Linux or WSL I'd choose WSL 9 times out of 10.
Honestly I feel the Windows hate is forced or due to self-inflicted issues.
I have a number of both. I like WSL for when I'm working in Windows and need to run some quick bash and handle the output in Windows file explorer.
Today I'm working on a project that runs bash scripts in WSL; it utilizes multiple unbound servers (that run in Ubuntu minimal and in pfsense).
They are very afraid of replacing Linux with windows, don't know how it's done, what it is etc.
Or they prefer the GUI in Windows like some people prefer the GUI from Apple. Those preferences still exist.
I would switch over to WSL in a heartbeat if speeds were 60-80% of bare Linux (cpu/memory) and every other subsystem was interoperable / accessible with Windows (cough network) which was my main issue with WSL, anything that wanted to run services was a disaster in WSL (DB/exposing port to host/etc).
For example, you can't pry KDE out of my cold, dead hands, ever. The capabilities of the desktop and the standard KDE installation blows anything I have used out of water easily.
We (as in Linux users, sysadmins and devs) love our TUIs because they work transparently over SSH. I have more than 100 servers which I reach regularly. I neither want to install a full graphical user interface, nor forward it to my desktop to manage them.
If you want to discuss this, I'm chill & all ears.
I have many Windows, FreeBSD and Ubuntu instances in use. They're all pretty great but none are the best fit everywhere.
This is a compatibility problem with my hardware. I couldn't believe all issues just went away when I switched over
On the other hand, given raw Linux or WSL, I'd choose raw Linux 20 times out of 10.
While I had my fair share of problems, for the last 20 years, Linux allowed me to be closer to hardware, allow me what I want to do with it and even more stable and performant than a "rock solid" Windows installation. I dual booted Windows and Linux until ~2022 IIRC, just for gaming, and no, I don't miss that bloated thing.
I have a Windows Laptop for my wife and a VM for specialized software which has no Linux counterparts, and even that limited exposure is enough to remember why I don't miss that thing. The experience is inferior to what I have on Linux.
> Honestly I feel the Windows hate is forced or due to self-inflicted issues.
Uh, no. I can't self inflict ads, bloat, performance issues and other papercuts by installing from an official ISO, using my legitimate license, and playing the Microsoft's way of using my online account during install. These are bundled with Windows itself. I even didn't install Microsoft PowerTools to these installations. They are "that" vanilla.
I stopped using Windows when I got an update prompt while playing a game that had two options I had never seen before, and was shocked to see at the time: “Now” or “Ok”. After clicking “Ok” the system waited a few minutes and then rebooted, causing me to lose the game, and get issued a short ban for leaving a game. And that was just the final straw. A few months prior, a Windows update corrupted two drives (NTFS) and I wasn’t able to repair them. Probably six months before either of those I was left with an inoperable system after a botched driver update for my (NVidia) GPU that caused me to do a full reinstall. Those are just issues I can remember.
Windows was a nightmare for me, in a way Linux has not been. In fact Ive had such a good time in Linux, I stopped buying Macs as well.
It’s not self-inflicted or being forced to hate windows, it’s just that for a lot of folks, myself included, Linux is a measurably better experience. If Windows works for you, that’s great, congrats I’m happy for you. But I think it’s weird to say Windows hate is forced or self-inflicted.
It's also just plain disrespectful to users. For instance, having to hack the installer to allow for local user accounts, forcing edge on me constantly to the point where even when I change the default browser, things still load in edge, and it still reverts my settings on occassion. Using Windows actively makes me hate microsoft. I'm mostly just on Linux and Mac now, I only use Windows when I absolutely have to.
Linux does have annoying technical issues to fix on occasion, but I'm a lot more tolerant of them because I feel like the creators of it respect me and my rights, whereas Microsoft treats me like I'm renting my own computer.
Windows has hundreds of milions direct users worldwide.
If it was that unstable as HN tries to make it, then a outrages would be in news every week
A BIG chunk of these are captured users working at Big Corp™.
I work at a company of 100k+ employees. The enterprise-managed Window machines we're issued are unbelievably bad. But I'm 100% sure if Microsoft pulled a Darth Vader "I'm altering the deal, pray I don't alter it any further" and 10x'd the price, nothing would change. Maybe at 100x (or the point of actual unaffordability).
This is how it is with a lot of modern tech, btw. Most people just suffer using it.
Similarly, interest in restoring/repairing older vehicles has increased because people are so fed up with using modern cars.
I drove a modern long-wheelbase Ford Transit last week when I moved house, and the whole experience was constant annoyances. Often the tech wasn't working correctly. I daily drive a 30 year old vehicle (which runs perfectly btw) and wasn't aware of how bad modern annoyances are.
e.g.
- The backup camera didn't work properly.
- The speed warning was incorrect, e.g., it thought I was speeding when I was actually 10 mph under the speed limit. The speed limit on that road has been the same for at least 7 years, and the van was 4 years old.
- Lane assist was constantly moving the wheels and taking over what I was doing. I was bang-on in the middle of the road. It was very jarring to have the wheel move when you haven't turned the steering wheel. It scared the absolute shit out of me when it first did it, I honestly thought there was play in the control arms.
- The driving awareness check said I was tired for some god knows what reason, and I had been driving for all of 20 minutes!
- It also said I wasn't holding the steering wheel when I had both hands on it.
- I couldn't feel the clutch biting point at all. Maybe the clutch was electronic as well.
- It had the most annoying electronic handbrake as well. Required you to hold the button before you could pull away the first time. This worked differently than if you were using it at a traffic light.
I know people that bought older vehicles (people in their 30s) because they dislike this stuff as well.
People just put up with this crap on Windows because they often don't have any other choice because, quite frankly, most people have no idea what Linux is and don't really understand how a computer works even at a basic conceptual level.
Spread it around. MS needs it's head screwed right.
Tried a few Linux distrod last year and had endless issues.
MS keep doing dumb stuff with the UI but there's tweaks to solve everything and it's similar to tweaking/ricing Linux so I didn't see any particular advantage of Linux.
NixOs is one that intrigues me though. I absolutely love the idea of OS as config files.
Unfortunately Nix seems to have so much drama and barely any 2 users can agree on the best way to do something.
I heard Rumours DHH/Omarchy might take a crack at simplifying/integrating Nix
Some user friendly Nix concept would make me switch asap
Manage to get through all of that, and I couldn't activate without signing into Microsoft because it took my key I had for Win 7 and used to upgrade to 10 and associated with my Microsoft account. So I had to basically use mass grave activator to fix that.
It then decided to rewrite my entire EFI partition (which wasn't on the same disc and had nothing to do with Windows) and give it a new unique identifier. This made Debian unbootable as a result, and I had to use a rescue USB to rebuild the EFI partition.
When I log in, everything wants you to log into Microsoft. The debloat script is now basically mandatory to have it work reasonably well.
Win 11 is just shit. I am not some sort of FOSS zealot. I just got fed up of fighting Microsoft every time they did a major OS update.
Unfortunately I have some bad news for you about random device drivers on linux. I guess with AI you can now fix the driver upstream yourself though.
And with WSL, very easy to jump between any linux distro. Debian, Ubuntu, Alpine, Arch -- anything.
I’ve really enjoyed the switch so far, having attempted it a few times in the past and ended up going back to windows (once in 2003, another in 2012). It’s encouraging to see MS continue to get the developer experience right with improvements like this, but unless they make significant improvements to the OS itself, I won’t be going back.
I want to caution people though because I see posts like this all the time, but nobody mentions just how tough it is to mimic the "polished" look and feel of Windows in Linux. Even getting it installed in a dual-boot setup was an absolute nightmare. If it had not been for Claude, there's no honest way I could have made this transition. It would have ended just like all my other previous attempts: going back to windows.
Here's a list of issues I documented along the way (with many more that I didn't document), some of them resolved with other methods (I game on Windows VM with GPU Passthrough now) and some I live with:
- Not able to choose same display resolution as Windows, especially when mirroring my laptop to my monitor. Most offered resolutions are too slow or too blurry with text also.
- Having to force browsers to use my dedicated nvidia GPU instead of the Intel one, rendering simple web games in browsers is still choppy even with this solution.
- Choppy games (RDRD2, Last of us 1 and 2) when using Proton/Lutris/Wine despite 3080 GPU (these games run smooth in Windows). Kind of expected this...
- Blocky artifacts showing up in most games (tried multiple drivers and Proton flavors)
- Have to disable secure boot in BIOS for some reason otherwise bootloader doesn't work
- Come up with hacky solutions to not get prompted for root password every time I connect a removable drive that is Bitlocker Encrypted
- For some reason when shutting down/rebooting, my CPU fan just stops cold turkey and it makes a "thud" noise. I've found no resolution and it only happens with linux.
- I can't control where applications on my taskbar live. If I place a pin in the middle and click it, the app launches a separate instance at the far end of the taskbar. Tried different sort options, no fix. Some apps work fine, others don't.
- Can't click shutdown/reboot when screen is locked. Need to click "Switch User" first.
EDIT: should mention some other pain points: support for broken software is very slow moving due to so many distros and flavors. If you update a package for security reasons and it breaks functionality, you could be stuck waiting quite a while (sometimes a month) for it to get fixed.
Also earlier this week CachyOS black-screened users that updated their OS, we could not even get to the login screen. The solution for me was obvious, just rollback to a snapshot, but some people couldn't even get that to work. When users complained or offered solutions, I saw one of the mods get snappy and basically blame users for updating too quickly. I mean, I get WHY that would occur, but it seems like such a weird thing to scold people for. The community is still very abrasive to Linux newcomers, but this has been the case for decades.
I went with Arch and wanted to take a few days to actually go through the Wiki and setup something completely from scratch and learn along the way. I had my laptop next to me and AI was a huge help. I went with Hyprland(Fish for shell, Kitty for terminal, Ashell for my bar, Walker for launcher, Yazi for explorer) and tried installing a bunch of pre-made .config files, but that was a big mistake, just take the time and get everything setup yourself, it's worth it in the long run to learn how all this works under the hood.
I think it's important to point out that my switch was also motivated by a desire to learn about the guts of a linux system and not just go with Ubuntu or a ready made one. I run Ubuntu on a home server and it runs great, but I am a full blown Arch snob now and I could never daily drive it.
Now there is virtio support, finally no need to depend on external CLI tools for what should have been in the box on day on.
Until now, even for Windows containers, we needed some Docker compatible CLI tool.
They're missing things like winget as well, but that's mostly an inconvenience rather than a blocker.
Upgrade the container host? Re-bake your container images. It's a massive pain in the ass.
So, for example, you cannot run a Windows 2019 container in a Windows 2025 host (nor the other way around). So, upgrading a base image means upgrading all the containers running in that host, and also the host itself.
EDIT: stumbled on the previous HN post here: https://news.ycombinator.com/item?id=49970507
Unfortunately most companies are too cheap to pay for Docker Desktop, and having Windows containers depend on a third party tool has been a problem in such customers.
Because using Rancher Desktop or Podman isn't also a given, due to similar issues.
NRR-WT1; wsl --version
WSL version: 3.0.1.0
Kernel version: 6.18.40.1-1
WSLg version: 1.0.79
MSRDC version: 1.2.7214
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26300.9457
NRR-WT1;Perhaps it reflects the amount of work and thought that has gone into it, but I really think the optics are better if the selling points are immediately obvious to the user.
Hopefully some light will be shed in further blogs.
On Ubuntu starting in 2006 and Kubuntu the last several years, what you're describing doesn't and hasn't happened to me.
When I've tried other distros over the years, the issue you described has happened to me on:
Red Hat Enterprise Linux
Fedora
SuSE
Debian (yes, even Debian but it was with the unsupported drivers and the issue was in a WiFi driver)
But it has not happened on Ubuntu or Kubuntu since I started using them in 2006. We use desktop Linux on several machines here and have for a long time, from Dell to HP to Lenovo.I bent over backwards for ubuntu, suse, fedora over the years. Sometimes it would be years of stability in between, but it would always come back to bite me if i ever tried to trust it as my primary machine.
No, that's not my story nor is it the story of the vast majority of Ubuntu/Kubuntu users.
> Too much variation in consumer hardware for linux to ever be reliable for majority.
That's a false statement, too many of us out here using Desktop Linux to try and make such a claim in 2026 (or even 20 years ago for that matter).
> I even bought lenovos officially linux supported laptop etc to try to fix the issues.
Tens of thousands of us developers in IBM used Desktop Linux on Thinkpads and later Lenovos for your statement to not ring true with me.
> I bent over backwards for ubuntu, suse, fedora over the years. Sometimes it would be years of stability in between, but it would always come back to bite me if i ever tried to trust it as my primary machine.
Those statements do not represent a truthful reality the majority of Desktop Linux users experience. This isn't 1996 in a random Linux IRC channel.
That's across various Ubuntu, Debian, Fedora, and even a crunchbang install.
In the past, especially on my custom desktop with uncommon GPU, sound card, and wifi chip, I'd check for compatibility and give it a few days after releases were announced to see if there were any user reported bugs. Knowing that devs prioritize compatibility for the most common devices first, I may have to wait my turn. If no, update. If yes, check for available solutions, update, apply solutions. If no solutions, wait.
But, for instance, currently I've been updating this Fedora 44 lenovo with the crunchy kernel roughly weekly for about a year, have been doing so blindly (just sudo dnf update && reboot before bed), and have not had a single problem in all of that time.
It's the same model as Windows- don't do shit before you know. You don't just install random garbage on a Windows machine, and you certainly don't allow automatic updates that re-enable features you've disabled, disable your ability to disable those features, break your menus, put ads on your lockscreen, put ads on your desktop, put ads in your menu, break hibernation, break wifi printing, or whatever other insane shit they've done in the last few years. You wait to update until you know all that broken shit has been removed or stay on XP until they pry it from your bloody knuckles or trust that some random dev doesn't have spyware in that de-bloated iso you've been thinking about.
Linux currently receives development from Intel, AMD, nvidia, google, facebook, qualcomm, amazon, and even Microsoft. Long gone are the days of the wild west governed by but a few.
Yes, for me today though this is usually fixed in 5min by Claude.
I found that seems like anything under /mnt/c goes through 9P
virtio is not enabled by default because its buggy in certain corner cases, and will be enabled by default when it stops doing that. That said, I do have that enabled, it is certainly faster.
Agents take more time than building Docker images.
vscode extensions using ripgrep in parallel in the background (there are many!) are killing the vm.
I now decided to follow Mitchell Hashimoto choice and use VMware Fusion and simply do all my work inside of it.
Source?
You can very easily measure this as well, use any disk benchmark
Without it, I can just as well ssh into another box.
Unless I'm mistaken, WSL to WSL2 was massive change in complete architecture, with WSL2 now requiring virtualization and making your host-OS run on top of hypervisor, with potential tradeoffs not many users are typically aware of. Basically, WSL and WSL2 were different beasts entirely :)
Was there anything that big or note-worthy from WSL2 to WSL3? Or just a natural evolution/upgrade?
The big addition here is the support for containers. The app now provides a simple way to run containers directly. Underneath the hood, there's still a kernel running on a VM, though. There's also some improvements to the filesystem layer, a kernel upgrade, etc.
This article[0] does a nice job explaining it.
[0] https://zenn.dev/yohakucode/articles/wsl3-wsl2-wslc-update
virtiofs is the biggest change, it was experimental in 2.x. It doesn’t affect my application, but most new users who want to share files between windows + Linux will see a huge bump.
This is great, this is some good work. But, like an issue I described before with Linux kernel io-uring[1], this fails to test and demonstrate performance with a healthy server load.
This obviously fails to depict a healthy server load because it's just way too specific.
There are probably better benchmarks.
auto mounting host disks in the guest is very nice.
Also, I prefer the .wslconfig parameters e.g. for kernel params, networking, memory + cpu caps. It's very convenient.
If you want a real bump in performance, I have a clever trick . Hardware isn’t cheap these days, so we demand the most of our software.
Good trick: get rid of the superfluous Windows layer which stands between that expensive hardware and your target OS. It takes up valuable memory, CPU time and storage space, introduces latency where you don't want it, exfiltrates data to unknown destinations and can decide to "upgrade" itself without warning.
Good tricks need catchy names to succeed so how about NoSL?
I came here to praise both Windows and Linux.
For me, Claude bypassed my sudo security by executing `wsl.exe -u root`. The Claude does not need any sudo password :)
I was very surprised this works, but that was Claude’s solution to editing a config file that needs sudo access without knowing the password (it edited /etc/fstab)
In summary, I really couldn't care less what improvements they make to WSL, and neither should anyone else, imho. If you want Linux, for the love of god just use Linux. Emulation works great the other way round by now.
We tested this in the office with equal laptops. CPU workloads have almost no VM overhead and the C++ / Rust compilation workloads on purely WSL2 virtual disk image is only 2% slower.
Yes WSL1 was more ambitious but the fundamental differences in the NT and POSIX makes it quite hard and CPU workloads suffered.
I've usually been able to get windows software running, but it's not always easy. I borrow my wife's laptop to reprogram my gaming mouse, for example. Couldn't be bothered any longer to dick about with wine.
But this is slightly beside the point: many have to use the allotted machines at work, which will tend to be windows (or maybe mac). That's the audience for WSL. It is an escape hatch for wage slaves.
The original WSL translated syscalls. It was a very tight integration. It was not perfect, and i should think it was a massive ongoing effort. I think it's an elegant approach bit i can see why wsl2 is essentially a vm. I never did any benchmarking, but i suspect that what wsl2 loses in disk performance, it gains in kernel performance. I never found either variant slow, and my corporate laptop was shit. My vagrant stack was diabolically slow, though.
I built my desktop. I do own an unused retail windows licence, and i think I've even activated windows on this box, but the key is not in the BIOS. I'm curious how that's going to work.
Tangent, in case my folly gives you a chuckle: my mouse, of the windows-only reprogramming tool, is a zerotes c18. I got busy with a dremel and did a _side project_ on it, only to discover that the thumbstick has only 1-key rollover. It's useless as a controller pad because it only supports the cardinal directions. I am a silly billy.
and I am using linux. When I execute code, it's executing via the Linux kernel, on the cpu . This is not an emulator . Intel has had hardware virtualization for ~ 25 years or more.
Why are you like this?
I don't think so. A PC with Linux is always the right choice. Macs don't even give you the option of a tower with a dedicated GPU, they are pathetic nowadays.
You can Linux all you want, I prefer Mac and I have done Linux extensively.
But once that crapware is exorcised, Windows can be useful.
It's a crappy company, like all corporate giants. It has a lot of crappy products. But the case is usually overstated.
* Windows Terminal
* Powershell 7
* Including OpenSSH client + server with windows
* the Visual Studio command line build toolset distribution
* Hyper V and bundling it with Windows Pro
* RDP
* MS Edge (basing on chromium, same extensions, same dev platform)
If something is slow on WSL, but not on bare metal linux, it means that the application is slop that only works when MAXING OUT your CPU, it's slop, the app is the slop
The Year of Desktop Linux is delivered on VMs.
Some things need to max out the CPU, certain compile steps for instance, that is not slop that is code doing its job. Others need significant IO, often random IO, certain other compile/link steps for example, that is not slop. Sometimes if you knew your code was likely to be run in a VM rather than on bare metal you might design it slightly differently to reduce its sensitivity to the detrimental effects, but not having done so doesn't make your code slop. There might be some room to blame slop for UI slowness as a lot of code out there updates their display in an in inefficient manner that is actually noticeable on bare metal too, especially when it unnecessarily uses 3D accelerated compositing or similar and something causes that to fall back to software rendering, but even then if it works well enough in the intended environment calling it slop is perhaps unfair.
You’d be impressed by how fast WSL runs. I’ve got other optimizations on the blog for even more performance tuning with pretty massive 2x-5x gains.
I am not sure what you are smoking, but that thing must be good.