3 ms·
Having used Piper, I think the Go package manager's approach is better, actually, at least for a collection of packages maintained by independent teams. If you
by skybrian 4y ago
Having used Piper, I think the Go package manager's approach is better, actually, at least for a collection of packages maintained by independent teams.
If you're not going to commit to fixing downstream packages for other teams when you change something, it doesn't make a lot of sense to have a monorepo. Instead, let people upgrade at their own pace.
- oivey 4y agoThis is a good way to put it. I think the opposite is also true: going with many repos means you are committing to other teams being on their own to upgrade. It’s difficult to know if you’ve fixed all downstream code if everything isn’t in one repo. That model makes sense for OSS. Not so sure about within companies.