Hacker News Reader

Chances are you will end up downloading a lot of dependencies anyways, why not have git deliver it all?

Huh? You'd download dependencies for the repos you need, not the code and dependencies for the entire company.

It could be several orders of magnitude larger and with a larger organization could be a lot of unnecessary code that any given Dev may never touch.

But imagine the increased productivity of your devs if they only had to check out a single repo. Anyone has the same organization of projects on their machine. All tools are in one place...

I don't understand. Where is the argument for more productivity?

We have one large-ish repo that keeps showing "This repository currently has approximately 547 loose objects.”

We keep pruning and gc'ing with different flags, but pulls just seem far slower than other smaller repos.

A: You avoid issues such as Readme files stating, "before compiling you have to git clone ../commonA, ../commonB". These always tend to get stale so in reality you also have to git clone ../commonC wasting you tons of hours of troubleshooting.

B: Developer working on daily basis in component A finds a bug in component B. He just has to change the code and commit it for review, instead of understanding the specifics of working with component B repository.

Reply on news.ycombinator.com