Of course, there are downsides to using a monorepo. I’m not going to discuss them because the downsides are already widely known and discussed.
I searched but I honestly can't find them. The only things I can think of are: implementation problems (repo too large, every git pull takes more time than strictly necessary for your project) and tainting tools like "git log".
Those don't seem very fundamental. Solvable by a "monogit" wrapper, if someone put their mind to it. Or are they?
Is there a fundamental problem I'm missing? I feel stupid for asking, given how matter of fact he dismissed it :(
EDIT: I guess what I'm trying to say is: monorepos feel, theoretically, like a strict superset of many independent ones. It's just the tooling that makes it less convenient.
I searched but I honestly can't find them. The only things I can think of are: implementation problems (repo too large, every git pull takes more time than strictly necessary for your project) and tainting tools like "git log".
Those don't seem very fundamental. Solvable by a "monogit" wrapper, if someone put their mind to it. Or are they?
Is there a fundamental problem I'm missing? I feel stupid for asking, given how matter of fact he dismissed it :(
EDIT: I guess what I'm trying to say is: monorepos feel, theoretically, like a strict superset of many independent ones. It's just the tooling that makes it less convenient.