HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
facebookarchive
mononoke
Systems & Infrastructure2017–2026
facebookarchive / mononoke · Archived

mononoke

A Mercurial source control server, specifically designed to support large monorepos.

16Distinct people
16Mentions
0Explicit recommenders
826GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A Mercurial source control server, specifically designed to support large monorepos.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year16 dated mentions

Observed mentions: 2017-07-28 21:23:10 UTC to 2026-10-16 13:27:12 UTC.

02462017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 6 mentions; 4 submissions, 2 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC642
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC422
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC413
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

16 sources
> ... back when Google built their version of this it wasn't possible for a team of seven to use LLMs to build a new custom implementation in five months... A quick look around tells us that Mononoke came from Facebook nine years ago. [0][1] Similarly, Piper was built long before LLMs were more than -at best- some very small scale implementations. Git was started in 2005. IIRC, it went from a blank editor window and some ideas in Torvalds's head to self-hosting in four days and managing the code for the then-latest Linux kernel release in two months. As I understand it, project staffing was also low; somewhere between one and a handful of people. Such amazing velocity and tiny staff size! <strike>Impossible without LLMs!</strike> I also note that you've weakened your claim from "build a new system from scratch" to "build a new custom impl
Read the rest
ementation ... that incorporated existing patterns". [3] > Here's the context for that "scandal" comment... Yes, that's the conversation that I wrote about. The rather unflattering start to that thread that you linked is important context [2], and the blog post you link to talks about the behavior you called "a scandal". I read all of the discussion for the first report, and most of it for the second. > I stand by my ["]original["] comment... Like many folks have mentioned to in recent months, occasionally saying "Jeez, that behavior is awful. Yeah, that's inexcusable." doesn't mean anything when you're back at bat for these companies a few hours later. [0] <https://github.com/facebookarchive/mononoke> [1] <https://news.ycombinator.com/item?id=16565299> [2] <https://lobste.rs/c/wk6js5> [3] The following paragraph from 'anthropic-mononoke-2' seems particularly apropos in light of how you've shifted your claim since I objected to it: *This makes Anthropic’s achievement significantly less impressive.* Anyone who’s put a distributed system into production knows how many issues tend to crop up during the productionizing process. “Our LLM built this thing, productionized it, and dealt with all the attendant challenges over 5 months” is a significantly more compelling narrative than “the source control team at Meta had spent 10 years building and productionizing this system, and we were able to point our LLM at it and rebuild it in 5 months”.
In Anthropic's Scion is heavily inspired by Mononoke
Google has published the git-repo tool[1][2], which is helpful for working across multiple git repos. Even with the tool there are significant pain points, though. In the longer term, I'm hopeful that VFS for Git[3] (from Microsoft) and/or Mononoke[4] (from Facebook) will reach a level of maturity that makes it easy to host large monorepos using open-source distributed version control systems. In the short-term most smaller organizations aren't going to hit the technical scaling limits of Git anyway. Most organizations could put all their projects in a single Git repo and not have any significant performance issues. Organizational issues like commit ACLs and code review enforcement are a separate issue, and often require additional tooling. [1] https://gerrit.googlesource.com/git-repo/ [2] https://source.android.com/setup/develop/repo [3]
Read the rest
In Why Google Stores Billions of Lines of Code in a Single Repository (2016)

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.