5 ms·
Thanks, but that's what was in the article. Why is this better than monorepo, specifically? What use cases does it allow that aren't possible in a monorepo? B
by solipsism 6y ago
Thanks, but that's what was in the article.
Why is this better than monorepo, specifically? What use cases does it allow that aren't possible in a monorepo?
BTW, the typically talked about giant monorepos do support branching, and the branch is never the entire repo.
- nickm12 6y agoA branch in a git repository defines a snapshot of the entire repository. You can't have two branches checked out simultaneously. If your repository has a file at a path, you can't have some part of the repository depending on that file at revision A and some other part of the repository depending on that file at revision B. Version Sets let you do that.
- solipsism 6y agoNot everything is git. Subversion lets you do that. So does perforce. And of course Google's monorepo has its history in perforce. Again... People making this claim that Brazil is so much better than monorepos seem to know a lot about Brazil but not much about monorepos.
- nickm12 6y agoBrazil was originally built on a Perforce monorepo. It didn't start being git until 2013 or so and even then packages could migrate between the Perforce repository and git repository. So Brazil is not an alternative to a monorepo.