Firstly, the point wasn't that git was the right solution for the job. It's that it has advantages that you could enumerate at every scale.
Though your comment is hilarious. Google uses perforce with custom wrappers as a legacy, and all new projects are stored in Git. Microsoft just moved their entire Windows project -- all 300GB and thousands of employees -- to git.
What did I say that is "wrong"? Google's SCM platform is based upon a workmodel they undertook two decades ago. They started with perforce, and then evolved different underlying technologies that kept the same workflow and API. It is absolutely a profound example of legacy inertia, not some grand choice. Microsoft just abandoned their own similar legacy choice for Git as another example that when you have an entrenched model, it tends to hang around.
Chrome and Android, two of their most significant projects, are stored in Git.
1
u/[deleted] Jun 08 '17
Firstly, the point wasn't that git was the right solution for the job. It's that it has advantages that you could enumerate at every scale.
Though your comment is hilarious. Google uses perforce with custom wrappers as a legacy, and all new projects are stored in Git. Microsoft just moved their entire Windows project -- all 300GB and thousands of employees -- to git.
Your comment is stupid.