4 ms·
If git is blocking you, you are using it wrong. Lotta instances of people treating it as an artifact repository. Use it correctly with a branching strategy that
by master_crab 2y ago
If git is blocking you, you are using it wrong. Lotta instances of people treating it as an artifact repository. Use it correctly with a branching strategy that works for your use case and it's bulletproof.
Plenty of other customers with the same magnitude problems as Meta are using Git perfectly fine.
- quicklime 2y agoWho are the others with the same magnitude as Google and Meta’s monorepos?
- disgruntledphd2 2y agoParticularly in 2014, when the git thing happened.
- master_crab 2y agoNo one. Because people should know better than to use monorepos. Most teams at Amazon (which works at the same scale) religiously avoided them.
- ec109685 2y agoMicrosoft has all of windows in a single repository.
- KaiserPro 2y ago> Plenty of other customers with the same magnitude problems as Meta are using Git perfectly fine. I mean there aren't. there are perhaps three places that have the same scale problem. A monorepo for a place with about 50k developers, that has been operating at that scale for 5 years. The current checkout if not sparse would be >80gigs The commit rate is > 20 a second. no amount of branching strategy is going to help on that. I love git, I used it professionally since 2010, but git is not a good fit for something _massive_
- ec109685 2y agoMicrosoft has made git work for massive repositories through a lot of blood sweat and tears: https://github.blog/open-source/git/the-story-of-scalar/ https://github.blog/open-source/git/the-story-of-scalar/