Excellent Reads

1443 readers

9 users here now

Are you tired of clickbait and the current state of journalism? This community is meant to remind you that excellent journalism still happens. While not sticking to a specific topic, the focus will be on high-quality articles and discussion around their topics.

Politics is allowed, but should not be the main focus of the community.

Submissions should be articles of medium length or longer. As in, it should take you 5 minutes or more to read it. Article series’ would also qualify.

Please either submit an archive link, or include it in your summary.

Rules:

Common Sense. Civility, etc.
Server rules.

founded 1 year ago

MODERATORS

Iliveonsaturdays@sh.itjust.works

awesome_lowlander@lemmy.dbzer0.com

AwesomeLowlander@sh.itjust.works

Why Facebook doesn’t use Git (graphite.dev)

submitted 1 month ago by Aatube@kbin.melroy.org to c/longreads@sh.itjust.works

9 comments fedilink hide all child comments

Monorepos, performance problems, and a lot of asking

you are viewing a single comment's thread
view the rest of the comments

[–] conciselyverbose@sh.itjust.works 11 points 1 month ago

Our code base has grown organically and its internal dependencies are very complex. We could have spent a lot of time making it more modular in a way that would be friendly to a source control tool, but there are a number of benefits to using a single repository. Even at our current scale, we often make large changes throughout our code base, and having a single repository is useful for continuous modernization. Splitting it up would make large, atomic refactorings more difficult. On top of that, the idea that the scaling constraints of our source control system should dictate our code structure just doesn’t sit well with us.

This is from the blogpost it links near the beginning. Also worth a read if you're interested.