Posted by sunshowers 1 hour ago
“Source control for huge monorepos has prior art, notably Google’s Piper and Meta’s Sapling, so we were able to build Scion with their hard-won lessons in mind.”
Mononoke is a component of Sapling, as I understand it. In fact, the repo link provided in this article links to a subdirectory of the Sapling repo. I’m not totally sure I understand the complaint.
To be uncharitable, this is marketing for Anthropic's impending IPO.
Another Claude-written article
This is the load-bearing seam.
And then I noticed some links to images from random small github projects and realized somewhere along the way agents had searched for existing projects and copied almost everything.
I wonder if something similar happened here on a larger scale.
There are two cases and only one is an issue for citations: - Mononoke was directly consulted and not attributed - Concepts were reinvented or used as a derivative (Sapling cited Mononoke and implements something similar)
For one I know Sapling, Git, and Jujutsu, but up to today I have never heard of Oxide or Mononoke and I am not exactly compelled to look up the research papers of any of them, at most I read through their high level documentation.
Whether it is plagiarism or hacking, the buck has to stop with the operators. It's not a good look.
I guess that is the case.
[1] https://en.wikipedia.org/wiki/Open-source_software_movement
> And, to be clear, I do not have a problem with Anthropic copying Mononoke’s design. (This is part of why we put out open source — to benefit humanity through the spread of good ideas.)
Followed by:
> But as LLMs continue to assist in designing new systems, they are likely to index heavily on existing designs. Mononoke is open source and in every LLM’s training set. If you ask Opus 5.5 or GPT-6 Astra (thanks Matthew Fowle) about prior art, they both immediately point out the similarities to Mononoke.
I think it is the duty of any responsible engineer to look for and cite prior art and related work, if only to compare notes.
Edit: I was too lazy. From the README: "Mononoke is the server built for the Sapling Source Control System"
1. Sapling can refer to either the system as a whole, or just the client people use (`sl`, forked from `hg`).
2. EdenFS is the virtualized FUSE filesystem (closely modeled after SrcFS at Google).
3. Mononoke is the distributed system that implements the backend server storage + the API they describe for checkout-less writes.
All three come together to form the core of the Meta source control experience. From what I can tell, Anthropic built its own version of 1 and copied 2 and 3, plus also built out a code review tool separately.
Another effort I couldn't have done without Astra. Even more so. All I did, the only reason I got cited, was because I'd asked Astra.
Centralized, virtual file system, all commits automatically on cloud, large binary files totally fine, Mercurial CLI. It’s fantastic. People who only use Git really don’t understand how much better things can be.
(Like GH finally has some support for stacks, 15 years late, with an implementation which is somehow more complicated and less powerful than the prior art...)
I agree so hard. It’s inertia is too strong and we’ve stalled progress for a decade.