4 ms·
if you didn’t experience issues with “vendoring” you were either: extremely lucky, work on a very small codebase and/or on a very small team. to me, only the i
by mirceal 8y ago
if you didn’t experience issues with “vendoring” you were either: extremely lucky, work on a very small codebase
and/or on a very small team.
to me, only the idea of using a git submodule pointed to a repo that has all my dependencies is...
repeat after me: a source control system is not a dependency management system.
- ilovecaching 8y agoMaybe the first, but monorepos are used company wide and contain millions of lines of code. The monorepo approach and vendoring does work, and there are a lot of advantages to having everything work on each revision, you just need to be conscious of it.
- mirceal 8y agohah. no. unless you have proper build/release/test/deploy state-of-the-art tooling the monorepo approach is a disaster. google and other bigco have it? do you? there is a reason we modularize and version things in software. in the context in which you pull in external libraries you don’t control, using a monorepo is madness.