Monorepos and the Fallacy of Scale

Re:Monorepos and the Fallacy of Scale by aidenn0 on Tuesday January 08, 2019 @12:28PM (#18857390)

I imported a 20 year old SVN monorepo to git with 100s of thousands of commits and tens of thousands of branches/tags and it was under 10GB. Removing a few large .tgz files that were inadvertently committed brought it down to 5 GB.

Linux has 25Mloc and ~800k commits; I think the pack is on the order of 2GB?

I don't doubt that 40GB nightmarish monorepos exist, I'm just wondering how and why.

[ Parent | on HN ]

Re:Monorepos and the Fallacy of Scale by busterarm on Wednesday January 09, 2019 @01:07AM (#18862680)

Linux is a highly focussed project trying to accomplish a single thing well and with rigorous standards.

If you have 100 developers working average US work schedules and making 5-10 commits per workday (debatable number, depends on culture, but i'm averaging between the "big" commit and lots of small commits), you're going to end up with 100k commits _per year_. And many large startups have a multiplier of that number of developers and they're much, much messier than kernel devs.

Referencing the ideal case as counter-example is a bit silly.

[ Parent | on HN ]

Re:Monorepos and the Fallacy of Scale by aidenn0 on Wednesday January 09, 2019 @12:03PM (#18866386)

So the nightmare monorepos are caused by unfocused teams trying to accomplish many different things poorly?

[ Parent | on HN ]