News for hackers. Stuff that matters.
Re:We Put Half a Million Files in One Git Repository, Here’s... by prmoustache on Thursday June 16, 2022 @04:26AM (#31763683)
Can't those xlf files be stored in a separate repo or in an object storage and let the build system fetch them from there?
Re:We Put Half a Million Files in One Git Repository, Here’s... by necovek on Thursday June 16, 2022 @06:16AM (#31764320)
That wouldn't be called a "monorepo" then :D

Obviously, the problems they are solving (and admitting to solving) are due to their dedication to the monorepo.

With all the effort spent on working around the drawbacks, I really wonder what advantages they are seeing that make it worth their while?

Re:We Put Half a Million Files in One Git Repository, Here’s... by prmoustache on Thursday June 16, 2022 @04:42PM (#31770735)
Well, there is monorepo and monorepo. Git was primarily made to host code, not necessary artifacts. I would categorize those files as artifacts and in my opinion it would still be a code monorepo to have everything else on a single repo.
Re:We Put Half a Million Files in One Git Repository, Here’s... by necovek on Friday June 17, 2022 @02:34AM (#31774772)
They are code files managed by a different set of people (translators), not generated artifacts (as they explain elsewhere in this discussion).

If we are being pedantic, git was not designed to host multiple projects in a single repo (otherwise, git would have been a subdirectory in the kernel tree). But tools are made without knowing how they'll be used, and that's ok, so I wouldn't stress on what the purpose for monorepo was, but how it's used and what value it brings.

Re:We Put Half a Million Files in One Git Repository, Here’s... by prmoustache on Friday June 17, 2022 @11:51AM (#31780016)
>They are code files managed by a different set of people (translators), not generated artifacts (as they explain elsewhere in this discussion

Translations do not look like code to me. Rather human generated artifacts.

What I understand is there is a strong tie/match needed between versions of these translations files and the code itself, so I believe this is where having all in the same repo would make sense, having the translators update those file when code has been modified...

Re:We Put Half a Million Files in One Git Repository, Here’s... by ghusbands on Friday June 17, 2022 @09:54AM (#31778186)
I think it's relatively normal to include build artifacts in a monorepo when you don't want users to have to be able to build every single one. Especially if you don't want to have to buy a license for every developer for specialist software that only needs to be used by a few people.
Re:We Put Half a Million Files in One Git Repository, Here’s... by TameAntelope on Thursday June 16, 2022 @01:07PM (#31768451)
Given the religious nature of the "monorepo" vs. "not-monorepo" argument, I would venture a guess that suggesting storing these xlf files elsewhere would upset someone's notion of what a "monorepo" Should Properly Be.
Re:We Put Half a Million Files in One Git Repository, Here’s... by klysm on Thursday June 16, 2022 @07:08AM (#31764643)
Having them under version control seems very important. Monorepo makes that easy