Use multiple repos. It doesn't hurt you know. And you can have proper granularity
The costs of monorepo seem to be much higher than just dealing with inter-dependencies. And you can always group projects if it makes sense
Use multiple repos. It doesn't hurt you know. And you can have proper granularity
The costs of monorepo seem to be much higher than just dealing with inter-dependencies. And you can always group projects if it makes sense
I'd be happy to see a counter-example, but I've not seen one yet.
Heck, even most individual developers use multiple repos.
Monorepos are usually ok (and even talking about team/project granularity) until you outgrow it.
Buildsystems like one-repo-per-project much better than monorepos. (Shipping a fix doesn't require rebuilding "the whole world" for example)
Seems to me that Git wasn't thought out for "monorepos" at first place as a VCS. Also, these companies should either use something else or not do monorepos.