[develatio]

Can’t we split the packages into logical groups and maybe have 20 or 30 monorepos of 70-100 packages? I doubt that all the devs involved in that monorepo have to deal with all the 2500 packages. And I doubt that there is a circular dependency that requires all of these packages to be managed in a single monorepo.

[smashedtoatoms]

People act like managing lots of git repos is hard, then run into monorepo problems requiring them to fix esoteric bugs in C that have been in git for a decade, all while still arguing monorepos are easy and great and managing multiple repos is complicated and hard.

It's like hammering a nail through your hand, and then buying a different hammer with a softer handle to make it hurt less.

[crazygringo]

> all while still arguing monorepos are easy and great

I don't know anyone who says monorepos are easy.

To the contrary, the tooling is precisely the hard part.

But the point is that the difficulty of the tooling is a lot less than the difficulty of managing compatibility conflicts between tons of separate repos.

Each esoteric bug in C only needs to be fixed once. Whereas your version compatibility conflict this week is going to be followed by another one next week.

[wavemode]

At Amazon, there is no monorepo.

And the tooling to handle this is not even particularly conceptually complicated - a "versionset" is a set of versions - a set of pointers to a particular commit of a repository. When you build and deploy an application, what you're building is a versionset containing the correct versions of all its dependencies. And pull requests can span across multiple repositories.

Working at Amazon had its annoyances, but dependency management across repos was not one of them.

[spankalee]

> And pull requests can span across multiple repositories

This bit is doing a lot of work here.

How do you make commits atomic? Is there a central commit queue? Do you run the tests of every dependent repo? How do you track cross-repo dependencies to do that? Is there a central database? How do you manage rollbacks?

[HdS84]

Thad exactly the problem. At least tooling can solve mono repo problems. But commits , which should span multiple repos, have no tooling at all. Except pain. Lots of pain.

[Vilian]

Don't forget that git was made for Linux and Linux isn't a monorepo and works great with tens of thousands of devs per release

[arp242]

> Linux isn't a monorepo

I assume you meant to write "is" there?