Getting Started with Git Bash

Re:Getting Started with Git Bash by MithrilTuxedo on Saturday February 05, 2022 @01:44PM (#30224308)

The enterprise bank I work for needs a business justification to spend resources to figure out if there's a business justification for allowing the installation of WSL. I asked in 2019.

Bouncing between my personal computers and my Windows work computer, what they've done to make git so slow... it makes me sad. On a brand new developer workstation, the git-prompt invocation in PS1 takes over a second to complete.

Developers who never used git before don't like it and I understand why. It's like a scene from Harrison Bergeron, like Git Bash has heavy objects strapped to it to make it at least as slow as everything else.

[ Parent | on HN ]

Re:Getting Started with Git Bash by michaelsbradley on Saturday February 05, 2022 @01:58PM (#30224507)

It’s owing to the high number of syscalls not being a big drag on Linux, etc. while causing noticeable slowdowns on top of Windows’ architecture/filesystem... something like that. A Microsoft engineer did a good writeup on it several years ago, if I remember correctly. I’ll try to find a link.

[ Parent | on HN ]

Re:Getting Started with Git Bash by michaelsbradley on Saturday February 05, 2022 @02:06PM (#30224618)

I think this is what I had in mind:

https://github.com/Microsoft/WSL/issues/873#issuecomment-425...

[ Parent | on HN ]

Re:Getting Started with Git Bash by agurk on Saturday February 05, 2022 @02:02PM (#30224567)

I was recently in a very similar situation to you and found that the $PATH of my git bash contained a network drive. Removing this for me made it still slow but useable.

This also made any programs I was running in it - like vim - useable too.

[ Parent | on HN ]