3 ms·
Interesting, RE: Google. Though, even if no other large-scale company is doing this, it seems on face value to be an easier and safer way to develop software up
by lhnz 5y ago
Interesting, RE: Google. Though, even if no other large-scale company is doing this, it seems on face value to be an easier and safer way to develop software up to perhaps a medium scale system/problem (and assuming that you're not needing to make database changes). I've yet to see a benefit to straddling changes across multiple repositories...
- andyferris 5y agoThe benefit of changes straddling repositories is having separation of control. For example different npm (cargo, etc) packages are controlled by different entities. Semver is used to (loosely) account for compatibility issues and allow for rolling updates. A single company requiring multiple repositories for control reasons might be an antipattern and might indicate issues with alignment/etc.
- lhnz 5y ago> The benefit of changes straddling repositories > is having separation of control. Good point, although a monorepo with a `CODEOWNERS` file could be used to give control of different areas of a codebase to different people/teams.
- jyounker 5y agoMonorepo tooling (as opposed to a big repo with a bunch of stuff tossed into it) generally provide access controls. Also remember that non DVCS repos generally have find-grained access controls.