Earlier quoted context omitted.
Half-finished releases haven been Microsofts SOP since forever. And especially for payware, bugs are only fixed in the next release, so you need to buy the subscription or the new release.
Really? https://github.com/microsoft/WSL/issues/4619 https://github.com/microsoft/WSL/issues/6069
WSL2 corrupting Git repositories and shell history
171–180 of 423 posts
Re: WSL2 corrupting Git repositories and shell history
#172I 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 don't think calling it WSL2 was a mistake. It wasn't something that was good for the users, but it had a very clear benefit for the people working on WSL: calling it WSL2 allowed them to close WSL1 issues en masse as "fixed in WSL2" and never look at them again.
Re: WSL2 corrupting Git repositories and shell history
#173Earlier quoted context omitted.
> Yeah I think you nailed it there actually. That's exactly their modus operandi. They're following the "rules" from "The Cathedral and the Bazaar", remember. Specifically, the "Release early and often" bit, for the purposes of this conversation. Microsoft are considered "good open source citizens" because of the changes they've made to follow the written non-rules as well as the the unwritten rules. If you're going…
The thing is 99% of what I get elsewhere does actually work properly. Microsoft are just excessively bad at this.
Re: WSL2 corrupting Git repositories and shell history
#174Re: WSL2 corrupting Git repositories and shell history
#175> Feel like booting Linux on a separate disk because of these issues. It always seemed strange to me that people would rather use WSL than the real thing when Windows doesn't bring much advantage. What am I missing ?
Visual Studio.
The other thing on my Windows VM is Affinity Photo/Designer (because GIMP is not a realistic Photoshop alternative).
Re: WSL2 corrupting Git repositories and shell history
#176Earlier quoted context omitted.
Is this the reason why they have deprecated shared folders in Workstation 16?
I don't think they deprecated shared folders, only shared VMs (a function that enables Workstation to act as a virtualization server). Source: https://en.wikipedia.org/wiki/VMware_Workstation#Version_his...
To be fair, this feature always felt..rickety. But it was very nice.
Re: WSL2 corrupting Git repositories and shell history
#177Earlier quoted context omitted.
My guess is it's the result of shutting down the virtual machine that runs the Linux kernel too soon, leaving writes to the virtual hard disk in an inconsistent state. This coincides with "shutdown /r /t 0" being able to cause it as well as blue screens or power loss. And explains why I've never seen it, despite using WSL2 on insider preview builds on multiple machines daily: I almost never shut down, only for update…
The kernel should and can handle unexpected ahutdowns without corruption. Data loss sometimes, but not corruption.
Which results in a corrupted repository, from Git's point of view.
Re: WSL2 corrupting Git repositories and shell history
#178I 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…
If you drop WSL then you get confused branding of what they are. WSL1 and WSL2 make it pretty clear you're getting the Hyper-V thing for the latter and the former is a Linux sys call API layer. I'm actually surprised they can't be used together.
Re: WSL2 corrupting Git repositories and shell history
#179Earlier quoted context omitted.
Yeah I think you nailed it there actually. That's exactly their modus operandi. What's even worse is they have managed to abstract most of the support away in this cycle. You can't get enterprise support now because they gutted that entirely. You can't get them to do anything on github because they keep moving all the projects around and erasing them all or auto closing the tickets and no one on first line support kn…
> Yeah I think you nailed it there actually. That's exactly their modus operandi. They're following the "rules" from "The Cathedral and the Bazaar", remember. Specifically, the "Release early and often" bit, for the purposes of this conversation. Microsoft are considered "good open source citizens" because of the changes they've made to follow the written non-rules as well as the the unwritten rules. If you're going…
Re: WSL2 corrupting Git repositories and shell history
#180> Feel like booting Linux on a separate disk because of these issues. It always seemed strange to me that people would rather use WSL than the real thing when Windows doesn't bring much advantage. What am I missing ?
> It always seemed strange to me that people would rather use WSL than the real thing when Windows doesn't bring much advantage. Windows brings lots of advantage to some things (including interfacing with the large number of people who rely on people having software that works only or best on Windows; in anything other than very tech-focussed firms this probably includes your employer, and even in such firms it often…