Mercurial 4.0 Sprint Notes
I know this is slightly tangental but I&#x27;m always a little shocked that Facebook (and I think Google to some extent) have massive mono repositories.<p>The benefits of having one repository do not seem to be worth the serious performance issues as well as potential coupling that can happen with a gigantic code base as well also making much more difficult to OSS certain parts.<p>e.g. why doesn&#x27;t FB use dependency management (or binary package management aka maven, npm, etc)? That is have multiple repositories and cut releases. Build tools to help cut and manage the releases and dependency graph of the releases.<p>There are even plugins and shell scripts that will make Mercurial act like a mono repository for many small repositories (I use it for our own Java Maven code base).<p>I must be missing some killer features and would love to see it in action (FB major repository).