Yeah, that's what I meant by "morphing dependency management problem to a source control problem". With a monorepo dependency management is way easier! But, sometimes:
- git on large repo 100% pain 0% fun. hg is slightly better, but not much.
- No version means no prebuilt libraries, which translates to "you need a great build cache to keep build time reasonable".
- "passes all the tests everything is good" if only we can run all the tests on such changes.
- People hate coordinating on imported/pinned third-party dependency versions, sometimes you need tools for large-scale automated changes to make progress, but :(
- Similarly, not all places make all their codes accessible to all engineers.
i.e. source control problem is, sometimes, harder.
- git on large repo 100% pain 0% fun. hg is slightly better, but not much.
- No version means no prebuilt libraries, which translates to "you need a great build cache to keep build time reasonable".
- "passes all the tests everything is good" if only we can run all the tests on such changes.
- People hate coordinating on imported/pinned third-party dependency versions, sometimes you need tools for large-scale automated changes to make progress, but :(
- Similarly, not all places make all their codes accessible to all engineers.
i.e. source control problem is, sometimes, harder.