Only in the open source world and a few SV darlings.
I am yet to do a project at a Fortune 500 among our customers that isn't based in Subversion or TFS.
I have been using Git only on personal projects.
From a technical standpoint I'm constantly amazed at the sheer diversity / museum of stuff that'll get deployed to prod in the Fortune 100. Sure, 80%+ of the stuff made in the past 15 years is all Java crud, but the nice thing about that is that dropping wars into an application container is a very solved problem. I don't have to really think during another 90s-style deployment where more difficult problems are metaphysical like if I'm actually still myself from 20 years ago dreaming very hard that I'm living 20 years in the future and this is a side-effect of my 90s frame of mind.
In the last year I've built internal-only systems for two Global Fortune 100 companies, both of them in Git.
I believe you are very incorrect.
They are questioning whether that generalization follows from your observations (using observations of their own).
Writing statements about Git's adoptin on HN posts don't make them into facts, unless they are baked by actual numbers.
The fact is that both of us are wrong, because neither of us have the data of those 500 companies, only anecdotes.
That would make both of you undecided. But one of you is right and the other wrong.
> Only in the open source world and a few SV darlings.
This statement is _factually_ incorrect. None of the companies I've worked for/done work for/communicated with were in SV and _all_ of them used Git. AKA it is in fact _not_ just "a few SV darlings," because the companies I've mentioned that use Git were neither of those things.
You'd be surprised. The vast majority of enterprise programmers have neither used it nor care to.
I think a bigger issue, though, is that some of these skills are very valuable, and some of these skills are the ones companies hire on, and those two sections are not always the same. Personally, I see myself as being somewhere around the n level on the algorithms stuff, but well into the log(n) level at the engineering/communication stuff. I've harped over and over on the weirdness of prioritizing theory knowledge over practical skill in day-to-day jobs where the practical is what matters - it's nice to see all the different dimensions so clearly laid out and given (roughly) equal attention.