Live data from Hacker News

WSL2 corrupting Git repositories and shell history

github.com

1–10 of 423 posts

Re: WSL2 corrupting Git repositories and shell history

#4
post #2

More: - WSL2 sometime corrupt .zsh_history and git https://github.com/microsoft/WSL/issues/5026 - WSL2 corrupts ext4 filesystem https://github.com/microsoft/WSL/issues/5895

But why? WSL1 was something like wine but reverse, but WSL2 is actually linux.

Re: WSL2 corrupting Git repositories and shell history

#5
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!

Lower overhead, and full integration with the host filesystem I believe are the 2 primary reasons many use it

Re: WSL2 corrupting Git repositories and shell history

#6
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!

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 compatibility layers.

Re: WSL2 corrupting Git repositories and shell history

#7
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!

I guess you'll have to use it to "believe" ;)

Setup is much less hassle, startup is much faster (one or two seconds) and resource usage is much lower than running Linux in a VM.

Also little things like VScode (running as Windows UI application) automatically detecting WSL and setting itself up to connect to the WSL side. To do the same for a VM requires at least to configure the SSL ports on the VM.

Re: WSL2 corrupting Git repositories and shell history

#8
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!

I guess you'll have to use it to "believe" ;) Setup is much less hassle, startup is much faster (one or two seconds) and resource usage is much lower than running Linux in a VM. Also little things like VScode (running as Windows UI application) automatically detecting WSL and setting itself up to connect to the WSL side. To do the same for a VM requires at least to configure the SSL ports on the VM.

Being light-weight won it for me. And the hassle free setup to use the same disk on both environments.

Re: WSL2 corrupting Git repositories and shell history

#9
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!

When I launch my WSL2 Ubuntu shell, I have a CLI prompt in Getting that same quality of experience under VirtualBox was nightmarish. Longer boot times, shared clipboard/filesystems were always breaking, random stuff related to hardening made update difficult.
Post reply on HN