3 ms·
> makes re-use of code harder I've found this to be a feature of polyrepos because monorepos can easily become a rat's nest of dependencies. Polyrepos make you
by dehrmann 6y ago
> makes re-use of code harder
I've found this to be a feature of polyrepos because monorepos can easily become a rat's nest of dependencies. Polyrepos make you think harder about what should really be exposed and shared.
- jonhohle 6y agoA phrase I like to use sums this up: “dependencies are easy to add, but hard to remove.”
- joshuamorton 6y agoBuild systems can enforce visibility, which solves this. Allowing fine grained visibility at the level of a file, package, or artifact is better than at the granularity of a repo.
- dehrmann 6y agoDepends how easy it is to change visibility. My point is polyrepos make things you need to be careful about like adding internal dependencies and API changes hard. Monorepos make those deceptively easy.
- joshuamorton 6y agoIt's not clear how a monorepo makes you changes hard (not why they should be). They're really easy when you can do them atomically, and even the hard cases are easier in a monorepo than multi. (And at least at Google visibility changes required the approval of the team who you want to depend on)