Another funny interaction I found with WSL2 and Windows is file case sensitivity leading to all sorts of weird error messages I wish I can use a real Linux installation but their display drivers don't work well with my multiple displays with different resolutions
WSL2 corrupting Git repositories and shell history
351–360 of 423 posts
Re: WSL2 corrupting Git repositories and shell history
#352Earlier quoted context omitted.
Are you sure this person is MSFT? There is zero information about them on GitHub.
Did MSFT start giving commit/moderation rights to outsiders on their repos? I assumed only MSFT org members can add tags to issues etc.
Re: WSL2 corrupting Git repositories and shell history
#353Earlier quoted context omitted.
Opposite anecdata - I got a gaming PC and i migrated all my development to it and WSL(2) has been a godsend. VS Code has a "WSL Remote" mode that works really well (where a vscode server runs in Linux and the windows GUI access it "remotely"). I even use the Windows Github app for the occasional GUI-assisted commit, and apart from being slow its fine. I've had only two problems with this set up: - Occasionally VS Cod…
Oh you need to fucking disable Window's Defender though, or add exclusions for your Linux distro/WSL2 folder, because when installing "node_modules" it will attempt to do realtime scans for threat-protection which absolutely cripples the speed. https://www.cicoria.com/improving-windows-subsystem-for-linu... https://www.reddit.com/r/bashonubuntuonwindows/comments/eok7... "I noticed a significant performance difference…
Re: WSL2 corrupting Git repositories and shell history
#354Earlier quoted context omitted.
Oh you need to fucking disable Window's Defender though, or add exclusions for your Linux distro/WSL2 folder, because when installing "node_modules" it will attempt to do realtime scans for threat-protection which absolutely cripples the speed. https://www.cicoria.com/improving-windows-subsystem-for-linu... https://www.reddit.com/r/bashonubuntuonwindows/comments/eok7... "I noticed a significant performance difference…
I see you this, and I raise you "the package repository I was mirroring contained an AV module that had a copy of EICAR in its test suite". AAAAAAAAAAAAAAAAAAAAAAAAAAAARGH.
Re: WSL2 corrupting Git repositories and shell history
#355Huh. I've used WSL2 and got extensively and never had any problems.
Re: WSL2 corrupting Git repositories and shell history
#356Earlier quoted context omitted.
That was long time ago, most people using VMware also use ESXi, and mainframes use type 1 as well. Just those using Virtual Box for free not.
> most people using VMware also use ESXi Most people using it are also using servers. Is ESXi on desktops/workstations anything other than very niche?
Where they are used is orthogonal to having knowledge.
Managing VMware installations requires having that knowledge.
Re: WSL2 corrupting Git repositories and shell history
#357Re: WSL2 corrupting Git repositories and shell history
#358Earlier quoted context omitted.
Sorry if this doesn't apply to you but how do you deal with Docker development? I've heard some horror stories regarding Docker for mac and I don't think I'll be able to live without my Docker containers.
I do that on an AWS instance. I have learned over the years to keep my desktop and my tools well apart as there have been some fatalities which have knocked me out for a day at a time before. I mostly write Go though which is fine on M1 macs.
Re: WSL2 corrupting Git repositories and shell history
#359Earlier quoted context omitted.
This is nothing specific to WSL though, Windows has always had this problem. I expect there are many Windows developers who have no idea how much time they spend waiting for their code to be virus scanned every day.
Some IDEs have started warning about this performance hit. IntelliJ + Gradle for example, but I'm guessing other Jetbrains products do the same.
Re: WSL2 corrupting Git repositories and shell history
#360Earlier quoted context omitted.
Or just install Humming Bird, working just fine for me since 2000.
Or just install WSL? What's the problem with Microsoft having an answer to this?
Because as proven by macOS and now WSL adoption, GNU/Linux would never have taken off if PCs already had a mature set of POSIX toys, given that its users care 0% about GNU/Linux, and would be deploying to HP-UX, Solaris, Aix, Irix, Tru64 just as well.