News for hackers. Stuff that matters.

A comment on Why Google Stores Billions of Lines of Code in a Single Repository (2016). Parent comment

Re:Why Google Stores Billions of Lines of Code in a Single R... by nine_k on Tuesday July 24, 2018 @08:13PM (#17605976)
Most folks who consider a monorepo don't have billions of lines of code, and often not even millions.

Linux kernel is a monorepo.

[ Parent | on HN ]
Re:Why Google Stores Billions of Lines of Code in a Single R... by threeseed on Tuesday July 24, 2018 @08:33PM (#17606054)
Linux kernel is one functional piece of work though.

Imagine if we combined KDE, Gnome, Linux Kernel, ZFS etc all in the one monorepo.

[ Parent | on HN ]
Re:Why Google Stores Billions of Lines of Code in a Single R... by dmoy on Tuesday July 24, 2018 @09:12PM (#17606235)
And gnucash, libreoffice, a couple copies of android, three other things that forked the linux kernel, and then all of apache to boot.
[ Parent | on HN ]
Re:Why Google Stores Billions of Lines of Code in a Single R... by rhencke on Tuesday July 24, 2018 @09:53PM (#17606375)
And we'll call it something crazy, like a Linux distribution!
[ Parent | on HN ]
Re:Why Google Stores Billions of Lines of Code in a Single R... by flukus on Wednesday July 25, 2018 @02:15AM (#17607202)
A linux distro is a bunch of package metadata and binaries, they don't push the code of every package into one repository.
[ Parent | on HN ]
Re:Why Google Stores Billions of Lines of Code in a Single R... by dmoy on Wednesday July 25, 2018 @01:17AM (#17607050)
No if it's Google that's much too reasonable of a name, you have to prefix and/or suffix a bunch of stuff on there.
[ Parent | on HN ]
Re:Why Google Stores Billions of Lines of Code in a Single R... by nine_k on Wednesday July 25, 2018 @06:13AM (#17608131)
Where there are obvious and pronounced functional boundaries, often backed by administrative boundaries, separate repos makes total sense.

Otherwise, it's an optimization; see "premature optimization" for cautions.

[ Parent | on HN ]