>> With multiple repos... having to split a project because it’s too big or has too much history for your VCS is not optimal... With a monorepo, projects can be organized and grouped together in whatever way you find to be most logically consistent, and not just because your version control system forces you to organize things in a particular way.
Uuuuh, if your one project has to be split because it's too big for your VCS, then you aren't going to make that thing smaller by putting multiple projects in with it.
>> A side effect of the simplified organization is that it’s easier to navigate projects.
That's a UI issue. Build a better UI, don't use a dirty hack, especially one that has other implications.
>> A side effect of that side effect is that, with monorepos, it’s often the case that it’s very easy to get a dev environment set up to run builds and tests.
With the growing trend of package managers being able to install dependencies straight from a git repository, I don't see this being an issue much longer. Again, this is a UI issue.
>> This probably goes without saying, but with multiple repos, you need to have some way of specifying and versioning dependencies between them.
Yeah, no shit, that's just good software development. The argument here is that a monorepo lets you be lazy.