this post was submitted on 15 Jul 2024
60 points (92.9% liked)

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:

  1. Common Sense. Civility, etc.
  2. Server rules.

founded 1 year ago
MODERATORS
Iliveonsaturdays@sh.itjust.works
awesome_lowlander@lemmy.dbzer0.com
AwesomeLowlander@sh.itjust.works
60
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
[–] jqubed@lemmy.world 12 points 1 month ago (2 children)

I’m not a programmer and don’t know how to use git, but at least have a basic understanding of what its use is. I think the Closing Thoughts has a pertinent lesson that’s much broader:

I’m reminded of the classic wisdom that so many of history’s key technical decisions are human-driven, not technology-driven.

Facebook didn’t adopt Mercurial because it was more performant than Git. They adopted it because the maintainers and codebase felt more open to collaboration. Facebook engineers met face-to-face with Mercurial maintainers and liked the idea of partnering. When it came to persuading the whole engineering org, the decision got buy-in due to thoughtful communication - not because one technology was strictly better than another.

[–] conciselyverbose@sh.itjust.works 2 points 1 month ago (1 children)

They made a point of mentioning the clarity and extensibility of the Python codebase as well (not sure if it was the article of the original blog) as making it easier to modify. They could have forked the code if they thought git was clearly better.

[–] Aatube@kbin.melroy.org 1 points 1 month ago

I wouldn’t expect web devs to know C.