News for hackers. Stuff that matters.

A comment on Why Google Stores Billions of Lines of Code in a Single Repository (2016). Parent comment

Re:Why Google Stores Billions of Lines of Code in a Single R... by hobls on Tuesday July 24, 2018 @08:39PM (#17606085)
There’s an important distinction between lots of code and lots of projects. I agree; if you have a ton of code you’d better invest in tooling. But if you just have several normally sized projects, a monorepo can make your life much more difficult than simply using several repos.
[ Parent | on HN ]
Re:Why Google Stores Billions of Lines of Code in a Single R... by rco8786 on Tuesday July 24, 2018 @08:57PM (#17606188)
Sure. You could also replace the term “monorepo” with “separate repos” and your statement would be just as valid. Either way you go has pros and cons.
[ Parent | on HN ]
Re:Why Google Stores Billions of Lines of Code in a Single R... by hobls on Tuesday July 24, 2018 @11:09PM (#17606665)
Agreed. I think the thing is that GitHub basically supports the separate repo approach fairly well out of the box. Using only a single repo requires more thought around your strategy, especially if you have multiple teams.
[ Parent | on HN ]