News for hackers. Stuff that matters.
Re:Why Google Stores Billions of Lines of Code in a Single R... by ori_b on Saturday January 11, 2020 @05:30PM (#22022828)
So is maintaining the greenness of a fragmented repo. The only difference is when you find out about the breakages.
Re:Why Google Stores Billions of Lines of Code in a Single R... by cipherzero on Saturday January 11, 2020 @07:43PM (#22023550)
Yes. Thank you! From my experience multi-repo doesn’t make problems go away, it just defers them and introduces others. I’m not against multi-repo or a strong proponent of monorepos... each have their strengths and drawbacks and there is a time and place for either. I struggle to deal with folks who firmly lie in one camp or the other.
Re:Why Google Stores Billions of Lines of Code in a Single R... by vanniv on Sunday January 12, 2020 @06:01PM (#22030296)
Agreed!

Multi-repo makes integrations harder, because you find out about breakages later -- which means that it might be harder to identify the cause and more likely that someone depends on the behavior that broke you by the time you notice it.

But, multi-repo makes local development faster and cheaper -- you're insulated from the churn of everybody else's check-ins. You don't have to constantly refactor everything every time some dependency makes a minor tweak.

You get more done and have a smoother development lifecycle -- but you're going to keep falling behind your dependencies unless you invest in keeping up -- and that part of the process is more unfun the less often you do it.

I currently live in a monorepo. I don't love it. But I've also not loved the multi-repos I've lived in, so... shrug