News for hackers. Stuff that matters.
Re:Why Google Stores Billions of Lines of Code in a Single R... by mnm1 on Tuesday July 24, 2018 @09:23PM (#17606282)
Slapping a whole bunch of projects into multiple repos with dependencies isn't a pleasant experience either. What is the solution then? I certainly don't want to host my own npm/composer/maven/clojars repos or even use those dependency managers to manage my own code which constantly changes and relies on multiple libraries both on the backend and frontend. I've tried this and, at least with a small team of two, it's not a pleasant experience at all. So how can I solve this problem? Cause the monorepo is very enticing after dealing with multiple repos and multiple dependencies pulled through dependency managers that clearly do not do well with dependencies that are constantly in flux.
Re:Why Google Stores Billions of Lines of Code in a Single R... by shakna on Tuesday July 24, 2018 @10:47PM (#17606586)
Re:Why Google Stores Billions of Lines of Code in a Single R... by glandium on Wednesday July 25, 2018 @12:31AM (#17606914)
Submodules are cutting edge and have cutting edges. The user experience on some corner cases can be painful. Example: if you happen to have unrelated conflicts when you rebase some patch across a submodule update, you're most likely going to end up committing a reversal of the submodule update.