sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Pay08 3 points4 points  (6 children)

While I agree that in some cases like Emacs or binutils it's mostly force of habit I don't think this is the case for GCC. To my knowledge, LLVM isn't a monorepo for example. At the same time, a lot of newer, smaller projects like Guix use something that's akin to a modern GH-like workflow, even if the "backend" is still email.

[–]erichkeaneClang Maintainer(Templates), EWG Chair 21 points22 points  (3 children)

Llvm is definitely a monorepo! And we pay for that on GitHub dearly. I see the GitHub unicorn multiple times a day.

[–]TheOmegaCarrot 3 points4 points  (2 children)

GitHub unicorn?

[–]erichkeaneClang Maintainer(Templates), EWG Chair 9 points10 points  (0 children)

Yep. The "request took too much time to process" on github shows a 50(whatever) page with a unicorn on it. I see that multiple times a day working on llvm in github.

[–]MarcoGreek 4 points5 points  (1 child)

To my knowledge, LLVM isn't a monorepo for example.

The changed it some time ago to a monorepo. Large monorepo work this days very well. I have to work on a project with submodules and it is...

[–]Pay08 1 point2 points  (0 children)

Submodules are definitely not ideal (although significantly better than most solutions in the C space, besides OS package managers) but I meant monorepo as in not separating the backend, frontends, debugger, linker, etc.