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

Programming

17309 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
[–] [email protected] 26 points 3 months ago (3 children)

Damn that sounds sick

[–] [email protected] 48 points 3 months ago

The source control was so smooth and pleasant that it convinced me that git isn't the be all end all, and the general developer focus was super nice, but some of that tooling was pretty janky, poorly documented, and you had no stack overflow to fall back on. And some of it (like EdenFS), really felt like it was the duct tape holding that overloaded monorepo together (complete with all the jankiness of a duct tape solution).

[–] [email protected] 42 points 3 months ago (1 children)

What you can do with 84000 employees

[–] [email protected] 19 points 3 months ago

And some good management. Probably not a common opinion around here, but my company is not a tenth of that size, with a hundredth the number of devs, yet different teams still end up copy pasting libraries. Because it's faster than convincing management DevOps is important.

[–] [email protected] 14 points 3 months ago (1 children)

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

[–] [email protected] 3 points 3 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.