3 ms·
That is a very uncharitable summary. The article discusses codebases being developed together or growing closer together over time, causing feature changes in o
by jorams 8y ago
That is a very uncharitable summary. The article discusses codebases being developed together or growing closer together over time, causing feature changes in one to need changes in another. It doesn't mention copy/pasting anything. They solved it by moving everything into a single repo.
Adding more repos would once again split up pull requests for features that touch multiple codebases, which is the reason they merged two codebases into one repo in the first place.
- bluGill 8y agoI will admit to being uncharitable. I am assuming they did copy/paste coding to get features into both. It is possible that they actually did write everything twice, but that is generally such a stupid idea I can't believe it (except for UI - it makes perfect sense to write a the UI for android and iOS completely separate - the logic behind the UI should still be common, but the UI elements/APIs are different enough that common probably isn't worth it) Adding more repos should not split up pull requests. If it does that is a function of bad architecture.