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

311–320 of 423 posts

Re: WSL2 corrupting Git repositories and shell history

#311

Post by mmis1000 »

samb1729 wrote: post #308
glandium wrote: post #305

Earlier quoted context omitted.

To give an idea how bad it is, building Firefox on a Threadripper 3970X on Windows takes slightly over 12 minutes if you don't disable Defender and somewhere around 7 minutes if you do.

What a horrible amount of overhead. Why does Defender need to scan the contents of a bunch of non-executable files? I suspect the answer runs deep and is at least somewhat horrifying.

Virus do abuse non executables like js, vbs, or whatever script file. Antivirus can't really know if it is the case without open it.

Re: WSL2 corrupting Git repositories and shell history

#312

Post by waheoo »

madeofpalk wrote: post #241
mrharshley wrote: post #225

WSL2 was promised as a good working extension for a Linux dev environment on windows by my peers. Sadly, a whole host of issues specific to my dev environment meant that it was useless as I’d spend more time fixing it than getting any valuable use out of it. More importantly, this became the very reason I switched to arch full time, and haven’t looked back since. I still hope that it becomes what it was promised to b…

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…

I don't really know if you can call running a remote vs code setup on localhost as opposite anecdata.

Isn't that just more of the same bullshit hoop jumping?

Everytime I hear about how great someone's wsl setup is I roll my eyes because it inevitably involves some rediculously convoluted wrangling to the nth level for something that is relatively basic on native Linux.

And these people rarely have an excuse for why they prefer windows over say fedora which has been a better than windows windows experience since windows 8.

Edit, wow even this thread people are suggesting the most drastic of things, let's run an entirely separate hard drive, oh but you need to fiddle with startup scripts because it couldn't be automatic.

Re: WSL2 corrupting Git repositories and shell history

#313

Post by mmis1000 »

proactivesvcs wrote: post #39
temac wrote: post #20

Earlier quoted context omitted.

> Running a virtual machine often means accessing the UEFI to be sure they have virtualization extensions enabled. Likewise for WSL2. I hope modern computers with a capable processor are all shipped with virtualization enable at firmware level, because Hyper-V can be used for tons of things in recent Windows.

Enabling hardware virtualisation opens up a significant and deep attack surface. Considering the vanishingly small percentage of users which benefit from it, I hope it stays off by default.

Well, android simulators do use hardware virtualization. And there is actually many people use them outside of developments.

Re: WSL2 corrupting Git repositories and shell history

#314

Post by month13 »

shrimp_emoji wrote: post #260
trinovantes wrote: post #168

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

>their display drivers don't work well with my multiple displays with different resolutions Unless you're writing through a time warp from 2004, this is not true at all, IME. But the statement is vague. "Work well" can mean some esoteric DPI scaling stuff that I think is only noticeable with 4K combinations. What distribution? What's "their display driver"? Nouveau, the open-source Nvidia one, is pretty bad, and ever…

I use a 1080p and a 4k display, it's pretty tricky getting consistent scaling per display.

Re: WSL2 corrupting Git repositories and shell history

#315

Post by naikrovek »

delusional wrote: post #159
naikrovek wrote: post #147

Earlier 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…

I think Microsoft gets more shit exactly because people expect more of them. They are the giants. they aren't a scrappy startup that needs to release or go bankrupt. Microsoft are seen as the safe choice, so their stuff has to "just work". That's obviously a bad place for innovation within Microsoft, but i don't really think anyone cares about the future of Microsoft.

People having high expectations of Microsoft is not Microsoft's problem. Microsoft are human beings just like the rest of you, and just like any large company, organizational inefficiency handicaps skilled developers a great deal.

Base your expectations on reality, and you'll have a much better time.

Re: WSL2 corrupting Git repositories and shell history

#316

Post by tester756 »

robbyt wrote: post #41
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.

could you name hyped projects that weren't supported or documented?

Re: WSL2 corrupting Git repositories and shell history

#317

Post by tester756 »

uncledave wrote: post #84
robbyt wrote: post #41

Earlier quoted context omitted.

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.

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…

>on github because they keep moving all the projects around and erasing them

who would've thought that managing hundreds of repos with shitton of issues, dependencies and people is difficult to get at 1st attempts

Re: WSL2 corrupting Git repositories and shell history

#318

Post by mst »

gavinray wrote: post #261
madeofpalk wrote: post #241

Earlier 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…

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

#319

Post by mst »

uncledave wrote: post #95
ncphil wrote: post #81

Earlier quoted context omitted.

Had a serious talk a Unix manager over a decade ago who was convinced Windows ops didn't require as much expertise as Unix/Linux. It was a common misconception that MS seemed to encourage. As someone who came over from Windows, I knew better. That attitude continues to influence standard practices, hiring and, most importantly, training and education opportunities for Windows admins -- to the detriment of all. I've a…

Agreed. I've done both and if you ask me Windows ops is vastly more difficult because everything is brittle, inconsistent and unreliable and rarely repeatable almost all of the time. It requires great skill, determination and persistence to navigate issues like this. Unfortunately as you suggest, the outcome is hiring as cheap as possible and fixing all issues by not changing anything other than replacing everything…

I've worked with good windows admins.

I have so much respect for them.

Re: WSL2 corrupting Git repositories and shell history

#320

Post by CamperBob2 »

ubercow13 wrote: post #266
gavinray wrote: post #261

Earlier 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…

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.

Try "every compile." If you wonder why your .exe takes a couple of extra seconds to start up the first time you run it after a build, well, this is why.
Post reply on HN