this post was submitted on 18 Jul 2024
130 points (97.1% liked)

Programming

17308 readers
254 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago
MODERATORS
snowe
Ategon
[email protected]
130
Why Facebook does not use Git – and why most other devs do • DEVCLASS (devclass.com)
submitted 3 months ago by AnActOfCreation to c/programming
65 comments fedilink hide all child comments
 
  • Facebook does not use Git due to scale issues with their large monorepo, instead opting for Mercurial.
  • Mercurial may be a better option for large monorepos, but Git has made improvements to support them better.
  • Despite some drawbacks, Git usage remains dominant with 93.87% share, due to familiarity, additional tools, and industry trends.
you are viewing a single comment's thread
view the rest of the comments
[–] FizzyOrange 2 points 3 months ago (1 children)

That's exactly the same in git. The old commits are still there, they just don't show up in git log because nothing points to them.

[–] aport 1 points 3 months ago (1 children)

Old, unreachable commits will be garbage collected.

[–] FizzyOrange 2 points 3 months ago (1 children)

Does that not happen with Mercurial? If not that seems like a point against it.

[–] aport 1 points 3 months ago (1 children)

I'm confused, the behavior you just said was "exactly the same in git" is now a problem for Mercurial?

[–] FizzyOrange 1 points 3 months ago (1 children)

I thought it was exactly the same based on the description.

[–] [email protected] 1 points 3 months ago* (last edited 3 months ago)

No the old commit is always there, marked as obsolete with the information of what it became. No holes in history. (Assuming you use the obsolecense markers)