Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WSL2 corrupting Git repositories and shell history

github.com

Post reply on HN
Print view View original

41–50 of 423 posts

Re: WSL2 corrupting Git repositories and shell history

#41

Post by robbyt »

crispyambulance wrote: post #23

I think calling it WSL2 was a mistake. The predecessor, WSL, "just worked" and it was more a less a linux experience for most practical purposes-- and certainly better than hoary old cygwin. This caused a lot of people to believe they could just transition to WSL2, lead on by the promise of an even more performant linux experience. The documentation didn't say anything about complications from attempting this, so a l…

Rushing half-finished products out, offering little/zero support is the new Microsoft.

The reason $MSFT loves open source is because they can get press hype over projects that are 75% complete (which is the main goal), and they don't even need to support it, document it, or make it actually work.

Re: WSL2 corrupting Git repositories and shell history

#42

Post by tarr11 »

crispyambulance wrote: post #23

I think calling it WSL2 was a mistake. The predecessor, WSL, "just worked" and it was more a less a linux experience for most practical purposes-- and certainly better than hoary old cygwin. This caused a lot of people to believe they could just transition to WSL2, lead on by the promise of an even more performant linux experience. The documentation didn't say anything about complications from attempting this, so a l…

Huh, I had the opposite experience trying to use wsl1 with a rails app, which required lots of workarounds.

Postgres never worked for example natively. Several npm modules would fail when running webpack.

wsl2 worked perfectly for these cases.

I wonder if people are mounting an ntfs volume in wsl2 which is really slow and janky?

Re: WSL2 corrupting Git repositories and shell history

#43

Post by rleigh »

harikb wrote: post #30
crispyambulance wrote: post #23

I think calling it WSL2 was a mistake. The predecessor, WSL, "just worked" and it was more a less a linux experience for most practical purposes-- and certainly better than hoary old cygwin. This caused a lot of people to believe they could just transition to WSL2, lead on by the promise of an even more performant linux experience. The documentation didn't say anything about complications from attempting this, so a l…

File system corruption is unforgivable mistake, but FS work is really hard to get right. Even stuff like VMware corrupts shared folders ... wherever they try to bypass a driver translation layer. Just Google for “vmware shared folder corruption”

Is this the reason why they have deprecated shared folders in Workstation 16?

Re: WSL2 corrupting Git repositories and shell history

#44

Post by snarfy »

crispyambulance wrote: post #23

I think calling it WSL2 was a mistake. The predecessor, WSL, "just worked" and it was more a less a linux experience for most practical purposes-- and certainly better than hoary old cygwin. This caused a lot of people to believe they could just transition to WSL2, lead on by the promise of an even more performant linux experience. The documentation didn't say anything about complications from attempting this, so a l…

I was using WSL to do esp8266 development so I could use linux tools. The official esp8266 windows toolchain is based on cygwin. If I'm using something that needs a unix environment anyway, why use cygwin when you have WSL?

I upgraded to WSL2 because well 2 is bigger than 1 so it must be better. But no, nothing worked. Serial ports are not supported in WSL2.

Re: WSL2 corrupting Git repositories and shell history

#45

Post by nijave »

bserge wrote: post #3

I don't really understand the use case for WSL. What are the advantages? You could run a full Linux VM and do everything on it on any machine these days. Which is what I do, but I'm just an old school hack. Anyone who uses WSL care to enlighten me? Thanks!

Business. For better or worse, there are plenty of places where the policy and tech allow WSL but installing a hypervisor on your machine is much more challenging.

WSL2 is basically just a Linux VM, though (I think it actually uses Hyper-V containers which seem to occupy some weird space between Linux container and VMs)

Re: WSL2 corrupting Git repositories and shell history

#46

Post by pjmlp »

jevgeni wrote: post #24
pjmlp wrote: post #6

Earlier quoted context omitted.

To sell Windows laptops to the same crowd that buys Apple laptops to develop GNU/Linux software, instead of supporting Linux OEMs, and are unhappy that Apple only cares about developers on Apple ecosystem. Microsoft understood that they only care about having some kind of POSIX support, and nowadays being Linux compatible is more relevant than straight POSIX, as the BSDs and IllumniOS also found out with their compat…

Or, alternatively, a crowd whose needs aren’t completely met by Linux.

Then why they develop GNU/Linux software to start with?

Re: WSL2 corrupting Git repositories and shell history

#47

Post by pletnes »

k__ wrote: post #33
crispyambulance wrote: post #23

I think calling it WSL2 was a mistake. The predecessor, WSL, "just worked" and it was more a less a linux experience for most practical purposes-- and certainly better than hoary old cygwin. This caused a lot of people to believe they could just transition to WSL2, lead on by the promise of an even more performant linux experience. The documentation didn't say anything about complications from attempting this, so a l…

Wasn't the main purpose of WSL2 to make WSL finally usable because before v2 it had really bad IO perf?

There are other issues, too. At least at some point, absolutely no haskell based apps would run, since their stdlib used some syscall which WSL1 did not implement. Broke pandoc for me. Stopped bothering with WSL1 there and then.

Other issues which colleagues encountered include abysmal performance and broken python installations as PATHs and other environment details are wildly mixed inside WSL.

I just don’t understand why some people were seemingly happy with WSL1, there were so many rough edges. WSL2 is much much better in my experience, on virtually all fronts.

Re: WSL2 corrupting Git repositories and shell history

#48

Post by quaffapint »

bserge wrote: post #3

I don't really understand the use case for WSL. What are the advantages? You could run a full Linux VM and do everything on it on any machine these days. Which is what I do, but I'm just an old school hack. Anyone who uses WSL care to enlighten me? Thanks!

Docker. Docker can use WSL2, so it works much nicer and less problematic than when running under standard windows emulation.

Re: WSL2 corrupting Git repositories and shell history

#49

Post by detaro »

pjmlp wrote: post #46
jevgeni wrote: post #24

Earlier quoted context omitted.

Or, alternatively, a crowd whose needs aren’t completely met by Linux.

Then why they develop GNU/Linux software to start with?

Because their needs aren't met by developing Windows or macOS software?

Re: WSL2 corrupting Git repositories and shell history

#50

Post by BlueTemplar »

jaltekruse wrote: post #14

MS is ridiculous, corrupting the filesystem is an OS mistake of the first order. Any systems developer should view corruption of a persistent storage system of any kind as totally unacceptable. And in this case the whole filesystem is open source! Meanwhile the open source people built a decent NTFS driver for linux years ago, I haven't seen what specs are released but I assume they needed to fill a few doc gaps to m…

Filesystems are hard :

https://danluu.com/filesystem-errors/

Post reply on HN