Microsoft and GitHub team up to take Git virtual file system to macOS, Linux
&quot;Git wasn&#x27;t designed for such vast numbers of developers—more than 20,000 actively working on the codebase. Also, Git wasn&#x27;t designed for a codebase that was so large, either in terms of the number of files and version history for each file, or in terms of sheer size, coming in at more than 300GB. When using standard Git, working with the source repository was unacceptably slow. Common operations (such as checking which files have been modified) would take multiple minutes.&quot;<p>These sentences in some parts gloss over the details, and in others it is flat out wrong. Git was designed for tens of thousands of developers (the Linux kernel), it was designed for huge numbers of files (but large numbers of files works fine on Linux due to the dentry cache, it sucks on Windows because they don&#x27;t have a cache that has the same behaviour as the Linux dentry cache). Admittedly it is slow for files that are large in size, but it was designed for source code;  what sane developer would have source files that are hundreds of MB in size?<p>That said, monorepos with several dozen software projects can be very slow due to O(n) functions such as git blame and the like. It&#x27;s true that git wasn&#x27;t designed for large numbers of projects in one repo that are only indirectly shared by library code and the like.<p>Unfortunately that was not written in the article.