- Proton, Copilot, and literally this single issue are what pushed people to Linux. If I were in charge there would be a team devoted to fixing this a decade ago.
WSL singlehandedly stemmed much of tide of developers moving away from Windows, but WSL native filesystem performance gave devs that magical experience when they boot into Linux the first time and see that the filesystem doesn't have to be ass. There's always been hacks around this, but for many devs the easiest hack was to ditch Windows.
They should have moved heaven to fix this on day one, there's really no engineering excuse. Linux is open source.
- Tangentially , I was a heavy used of wsl and moved to linux a few months ago and LLMs made most of the downsides of using linux as a desktop go away for me. I chatted with claude about the migration to find the best distro, decided on Fedora. After the install I asked everything I wanted to configured and got straight answers. In 3 or 4 hours I had an even more comfortable experience than I had on windows. AI made the annoying parts of trying to figure out how to edit all the config files to have linux behave the way you want very easy. I also had claude code write a bunch of scripts that I could have done but would probably never bring myself to actually do it . WHen you have a coding agent readily available , having an open source desktop environment makes a lot more sense. I encourage everyone to try it.
- What killed WSL for me was the incredibly janky way I had to share USB peripherals. usb-ipd works 80% of the time, all the time.
- If it is as good of an improvement as the first major update, it will be hard to tell from native.
Hopefully, they will just push it out to everyone asap. We make heavy use of symlinks into Windows drives.
by chris_money202
1 subcomments
- They are undoubtly doing this because so many users operate out of /mnt/c with zero clue of that implication.
by zaptheimpaler
0 subcomment
- I was trying WSL years ago and this is one of the reasons I just moved to a full linux server instead. We still have way too many problems interfacing across filesystems. I hope with AI we will see an iteration on ExFAT that has all the journalling, versioning etc. magic of modern FS' and can be adopted across all 3 OSes. Probably a long shot but I can dream :)
- Moved to mac about 7 years ago because of horrible WSL file system speed was.
- I was always disappointed with the design of wsl2. The wsl1 design of a syscall layer atop NT had greater architectural purity. They way I heard it, they introduced a virtual machine into the design specifically in order to bypass poor NT filesystem performance. I'm sure it's easier said than done, but it would have been nice if they instead fixed the issues on the NT side, rather than side step them with a VM.
- I switched from WSL (reconn'd to WSL1) to WSL2 because I thought that WSL1 would be abandoned.
However, the shell for WSL2 runs in a window that grabs things, such as ^V.
So, ssh from WSL2 (to AWS for example) is awkward. For exampl, Emacs on the AWS box is almost unusable.
by themeiguoren
4 subcomments
- I can’t find any benchmarks on this, anyone have a sense of the speedup that can be expected here?
And for what it’s worth, that version isn’t available yet when I try to update WSL.
- it's kinda shocking how both WSL2 file perf and Docker for Mac file perf are so horrendously bad that you can just tank performance and have a 3x better local dev setup on most projects by using "normal" Linux.... and yet it's been the status quo for so long.
I don't get how people are so comfortable with dev tooling being as busted as it is.
by politelemon
0 subcomment
- Nice to see a bit of good news here, WSL is an underrated component in enterprises, and quite often the only way you can get close to Linux. Windows and Macs feel like trading one cancer for another with different logos.
- I had no idea they used the Plan 9 file server for accessing files in WSL. I wonder what the original reasoning for choosing 9P was.
- counterpoint: WSL is great. I like it. I enjoy & prefer Windows desktop & Linux terminal. very happy.
by thot_experiment
0 subcomment
- Nice, FWIW this is currently pretty easy to solve by just keeping your stuff on a separate EXT4 volume and then mounting that under Windows. Windows accessing a mounted EXT4 volume through WSL is much faster than the other way around.
- Sick, I can stop using `pwd -P` based switching between /usr/bin/git and git.exe (and for some other stuff like ripgrep). Hell, I can probably stop using PowerShell completely.
by flumpcakes
0 subcomment
- WSL2 is honestly the only thing keeping me sane having to work with a Windows 11 desktop environment at work.
The new container capability also looks magical, and being able to access that directly from windows apps seems pretty cool too. Not sure it would be worth the time investment vs. docker desktop, but interesting none the less.
- WSL1 was really really fast! It was quite unique system too totally customized for the Linux kernel and windows interfacing!
Was really disappointed when WSL2 came along and just virtualized everything; fs performance took a shit.
Anyway I don't care about windows these days, all Linux all the time.
by agentultra
0 subcomment
- Do the audio buffers to the host device next!
by ranger_danger
0 subcomment
- Wouldn't using NTSYNC on the Linux kernel side also improve filesystem performance?
- Hasn’t this always been the case? I have always run builds under WSL2 in Windows because of this.
by mattkevan
1 subcomments
- Where are we on the embrace/extend/extinguish curve right about now?
by phendrenad2
1 subcomments
- Hopefully they're heading towards a "boot to Linux" mode.
- Any benchmarks and comparisons done? am I overlook it?
by thomasswilliams
0 subcomment
- Upgraded and saw faster WSL launches straight away
- i've never noticed slow file access through wsl, but ive also only used it to compile small c programs tbh
- Give me one good reason why anyone would bother with any of this at all?
by NoGravitas
1 subcomments
- Now if only Windows would also get faster Windows file system access.
- why don't they just switch completely to Unix, lol
- It's always good to see improvements around WSL2, but especially this one is not so relevant IMHO, since it only affects WLS2 file access to Windows file system. If you store your dev environment in WSL2 anyway, this won't help you.
Hacker News