>>>* They don't like to have to clone lots of other repos, and to then worry about their versions (in part because the tooling support for this might be less than great).*
I think this is the argument around which the whole post is made. Everyone does want to work in a small space where they control everything. I want to see git log with just my code commits - so I'll make a microservice out of it.
All other arguments are just there to wrap this one. I think it's wrong.
At an organisational level, a monorepo is more good than bad because it simplifies dependency management and makes for a low-ego team.
Counterpoint: monorepos make it easier to neglect packaging and dependency management since it's mechanically possible to assume any files in source control are on-hand. This makes it trivial to have implicit dependencies and see the uglier implications of Hyrum's Law.
I think this is the argument around which the whole post is made. Everyone does want to work in a small space where they control everything. I want to see git log with just my code commits - so I'll make a microservice out of it.
All other arguments are just there to wrap this one. I think it's wrong.
At an organisational level, a monorepo is more good than bad because it simplifies dependency management and makes for a low-ego team.