3 ms·
>Moreover the git maintainers were unwilling to work with Facebook to improve git to solve some of these problems. Mercurial was a better fit More add-on disc
by jasode 9mo ago
>Moreover the git maintainers were unwilling to work with Facebook to improve git to solve some of these problems. Mercurial was a better fit
More add-on discussion including Microsoft+Git spurred by your previous comment about this: https://news.ycombinator.com/item?id=15725497 https://news.ycombinator.com/item?id=15725497
From the Facebook blog post, it seems like the key issue was Facebook's internal filesystem monitoring tool (Watchman) was easier to integrate with Mercurial than with Git:
https://engineering.fb.com/2014/01/07/core-infra/scaling-mercurial-at-facebook/#:~:text=We%20solved%20this,with%20Watchman%20straightforward%2C https://engineering.fb.com/2014/01/07/core-infra/scaling-mer...
So, neither Mercurial-out-of-the-box nor Git-out-of-the-box could handle huge monorepos. But Mercurial's willingness to make some modifications made it easier for Facebook to integrated their custom tooling to avoid the slow Big-O O(n) scans for changed files.
- nextaccountic 9mo ago> From the Facebook blog post, it seems like the key issue was Facebook's internal filesystem monitoring tool (Watchman) was easier to integrate with Mercurial than with Git: > https://engineering.fb.com/2014/01/07/core-infra/scaling-mer https://engineering.fb.com/2014/01/07/core-infra/scaling-mer... That link is from 2014, is there any more recent work to make Git use a file watcher rather than scan the whole tree?