4 ms·

Why is that?

keybored 2y ago
All of Big Tech companies use hive repos, I mean monorepos, and Git can’t cope out of the box with that (except maybe at Microsoft since they have some people working on that).
- jasonpeacock 2y ago
  Amazon doesn't use monorepos. But then different tooling had to be created to manage dependencies and performs builds. You either have a large monorepo with special tooling, or many repos with special tooling. Either way, if you're a large company then you have special tooling...
- hocuspocus 2y ago
  > All of Big Tech Define all? Because that looks more like maybe half to me, at best.
  - keybored 2y ago
    * Half of all Big Tech.
- mhh__ 2y ago
  git can cope a lot better than some seem to realize. Obviously it chugs on a truly huge repo but this is genuinely enormous. Sapling if I'm not mistaken uses the same file structure as git.
  - aseipp 2y ago
    Sapling is a Git client, so it can use Git on-disk structures, if you ask it to. But its native backend, a central server system called Mononoke, is completely different in design and scope, and is in fact designed to handle very large repositories with working sets and data sizes way beyond what Git can handle. It's all a bit of a weird conversation because if you talk to an OSS programmer, a 5GB repository is "ginormous", and if you talk to some SV tech person working at corporate, they think a 300GiB repository (Windows monorepo) is reasonably large, and if you talk to a gamedev from a one off random studio, they think 2TiB is "pretty average." So you really need to be specific about the workload you're looking at.
loeg 2y ago
Big big monorepo and lots of effort invested in making mercurial usable with said monorepo. Off the shelf git wouldn't work. There's also 10+ years of operational experience with the mercurial toolchain and that has some value.
krunck 2y ago
Not Invented Here Syndrome https://en.wikipedia.org/wiki/Not_invented_here https://en.wikipedia.org/wiki/Not_invented_here
- mhh__ 2y ago
  Facebook seem to have a good track record of their "NIH"s being quite good by their own right. If you're prepared to spend money on it it's not that hard to beat a generic tool for your workflow.
steveklabnik 2y ago
https://graphite.dev/blog/why-facebook-doesnt-use-git https://graphite.dev/blog/why-facebook-doesnt-use-git The short of it was, way back in the day, the mercurial folks were more amenable to working with FaceBook than the git folks were.

Why is that?

All of Big Tech companies use hive repos, I mean monorepos, and Git can’t cope out of the box with that (except maybe at Microsoft since they have some people working on that).

jasonpeacock 2y ago
Amazon doesn't use monorepos. But then different tooling had to be created to manage dependencies and performs builds. You either have a large monorepo with special tooling, or many repos with special tooling. Either way, if you're a large company then you have special tooling...
hocuspocus 2y ago
> All of Big Tech Define all? Because that looks more like maybe half to me, at best.
- keybored 2y ago
  * Half of all Big Tech.
mhh__ 2y ago
git can cope a lot better than some seem to realize. Obviously it chugs on a truly huge repo but this is genuinely enormous. Sapling if I'm not mistaken uses the same file structure as git.
- aseipp 2y ago
  Sapling is a Git client, so it can use Git on-disk structures, if you ask it to. But its native backend, a central server system called Mononoke, is completely different in design and scope, and is in fact designed to handle very large repositories with working sets and data sizes way beyond what Git can handle. It's all a bit of a weird conversation because if you talk to an OSS programmer, a 5GB repository is "ginormous", and if you talk to some SV tech person working at corporate, they think a 300GiB repository (Windows monorepo) is reasonably large, and if you talk to a gamedev from a one off random studio, they think 2TiB is "pretty average." So you really need to be specific about the workload you're looking at.

loeg 2y ago

Big big monorepo and lots of effort invested in making mercurial usable with said monorepo. Off the shelf git wouldn't work. There's also 10+ years of operational experience with the mercurial toolchain and that has some value.

krunck 2y ago

Not Invented Here Syndrome https://en.wikipedia.org/wiki/Not_invented_here https://en.wikipedia.org/wiki/Not_invented_here

mhh__ 2y ago
Facebook seem to have a good track record of their "NIH"s being quite good by their own right. If you're prepared to spend money on it it's not that hard to beat a generic tool for your workflow.

steveklabnik 2y ago

https://graphite.dev/blog/why-facebook-doesnt-use-git https://graphite.dev/blog/why-facebook-doesnt-use-git The short of it was, way back in the day, the mercurial folks were more amenable to working with FaceBook than the git folks were.