this post was submitted on 18 Jul 2024
124 points (96.3% liked)

Programming

18193 readers
120 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 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
124
Why Facebook does not use Git – and why most other devs do • DEVCLASS (devclass.com)
submitted 7 months ago by [email protected] to c/[email protected]
63 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
[–] [email protected] 84 points 7 months ago* (last edited 7 months ago) (17 children)

Facebook uses Mercurial, but when people praise their developer tooling it's not just that. They're using their CLI which is built on top of Mercurial but cleans up its errors and commands further, it's all running on their own virtual filesystem (EdenFS), their dev testing in a customized version of chromium, and they sync code using their own in-house equivalent of GitHub, and all of it connects super nicely into their own customized version of VS Codium.

[–] camr_on 25 points 7 months ago (6 children)

Damn that sounds sick

[–] [email protected] 15 points 7 months ago (2 children)

And kinda horrifying. If something goes wrong, no Google, it's straight to IT

[–] computergeek125 4 points 7 months ago (1 children)

There's probably specific ticket queues and wiki/doc spaces for each support team.

Problem with an app? Send it to the internal dev/support team. Then if needed it gets routed.

load more comments (3 replies)
load more comments (13 replies)