“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.
If I credit my newly introduced car as inspired by Corvette, then sure, it might be ok not to mention the engine (Mononoke is the server part of Sapling)
However if my new car's engine is a near copy of the one in the Corvette, and my announcement gushes about the engine using the same terms the Corvette design team invented...
To me, this sounds like it's less about the technology, whether it's open source or not, and more about the people in the room that are influencing the design, direction, and implementation of it. All of which are very likely to have previous positions at major companies responsible for the products mentioned.
Perhaps if there is any ambiguity, it's intentional on the part of caution around intellectual property provenance.
The level of inspiration goes well beyond "hard-won lessons". Something like Lore (slop design document aside) can claim that level of inspiration. Here the data model is a direct copy, down to the terminology.
To be uncharitable, this is marketing for Anthropic's impending IPO.
> Here the data model is a direct copy, down to the terminology.
That’s not surprising to me - they designed and built it using their LLMs, of course it’s duplicating prior work. That’s essentially the core of what LLMs do, after all.
Effectively nobody considering buying into the IPO cares about Anthropic's source control system. They could be passing around floppy disks and so long as they were still shipping nobody would care.
When Fable first released, I had it "one shot" a project using an initial spec and a team of agents. I was blown away with how good the results were.
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.
I think a lot is memory really. For fun you can try pointing just about any model against the older kaggle challenges and it’ll come up with more or less the winning solution from memory. It’s here where you see a Gemma 27b perform about the same as opus 5.5
I've always worried about the level of "IP laundering" which is done by LLMs.
While that's not technically the case here (given Mononoke's license) it is still quite negative in my view. We will have fewer people wanting to share ideas openly since LLMs are so good at not only finding them, but also not attributing them. This also leads to a loss in diverse collaboration, which is probably one of the biggest drivers for good software.
Right now there's probably a lot of these "novel" ideas floating around which models can present as their own, but that's raiding our coffers with no inbound future stream.
Is this what is expected of how to cite sources? Because if this is the expectation nobody does it.
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.
Sapling does a bit more than cite Mononoke. And Oxide was not involved in Mononoke's development. These are kind of details that would not be expected of a casual user. However, when valuations soar into the trillions, we can expect companies with dedicated writing staff to communicate attribution properly.
Anthropic effectively doing a "git clone" with extra steps here.
Uncharitable?
I don't think so.
If this were about functionality, why not use Sapling/Mononoke or extend it and contribute back to the open source community?
Because that doesn't juice the IPO valuation.
I think it's worse than just IPO juicing. I think it's "look what our agents can do" and also pushing more on the "software engineers are becoming obsolete" line that Dario public-pronounces. Getting high on their own supply.
Projects seem to be getting approved or pushed there purely on the basis of showing off that they can vibe-build infrastructure.
Which.. yes, you can. But now maintain it. Understand it. Manage thousands of people using it. Those are part of the reasons we re-use proven solutions rather than rolling our own -- not just because the coding part is hard.
Same thing happened with the Bun rewrite. "Oh wow, look what we can do! What's that, nobody adult supervision telling us that this is a bad idea? Let's go!"
hi rain :) Anthropic’s post reminded me a lot of your work, glad this is getting some visibility. do you think the “time has come” for some of these ideas that previously may not have spread because they need too much learning to appreciate? I wonder what new norms will emerge in creative collectives.
Thanks! Yeah, I think overall several more organizations are going to reach the scale that Meta reached a while ago. I'm not sure if they'll go in the monorepo or polyrepo direction, though; I can see arguments both ways.
Whether the ant post amounts to plagiarism, it is definitely somewhere between extremely lazy and intentionally misleading. No particular idea has its inspirations or origins traced or cited, there is no comparison to comparable tooling or discussion of prior work, and there is absolutely nothing to actually position or discuss the project in a manner that might lead to "Contributing to the wider ecosystem."
If only they had had a claude write the post, it'd be full of citations, inspiration credit etc.
I really really wish Sapling could be used externally. It is by-and-large TheWay.
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.
Working for a few years at Facebook, and then returning to the normal world, it was like stepping back in time -- I really think that the mainstream git culture (by which I mostly mean "github") achieved a local maxima around 2012, and has been holding the industry back since :(
(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...)
As someone who came to terms with dying on the mercurial hill, someone who forgot more gitisms than there are to learn in the first place because git cli's inconsistencies and poor taste hurts and neuters my memory, yeah, I relate.
Most people aren't VCS nerds, most are of a generation that only ever knew git. Learning git was a prerequisite they engaged with out of necessity, not by choice, not after exploring the problem space and pondering about different approaches. Learning git was difficult, and the more they learned the more they discovered they had more to learn, including the little things, obscure details and a plethora of paper-cuts. For them (again, I suspect they are a majority), the perspective of learning something else comes with the expectation of a similar daunting effort and steep cognitive reluctance.
That's the paradox of git as I see it: had it been a simple and easy system to pick-up, it would probably have been replaced, and/or the VCS space would be much more competitive.
Hey Steve, I read your recent blogpost on the ERSC site - have you or David (or anyone else at ERSC) felt like there's a Rusty-enough topic around what your startup is doing to give a talk at Rust NYC/Rust conference soon?
There's not really a VCS meetup in NYC, but I got to hear David and others at Rust NYC wax eloquent about Sapling vs Piper and Buck vs Bazel a couple of times, so I think the audience is there!
They’re semi-adjacent in that they are about build systems that don’t suck. (buck2 is also mostly TheWay but also not usable outside of Meta and has room for improvement).
Save us from Git and CMake Steve! Please I beg you!!
Agents tend to act differently than humans here. I would have expected most humans to notice and acknowledge the connection. Passing it off as one's own insight definitely feels like plagiarism. Agents are generally not equipped to deal with this type of thing, since looking for prior art is a detour from their goal or an exercise in post-hoc rationalization of knowledge built into the weights.
Whether it is plagiarism or hacking, the buck has to stop with the operators. It's not a good look.
So, if I follow this correctly, Mononoke is a Facebook project. Facebook, now Meta, is widely known to be a company that steals stuff and doesn't give attribution.
The issue, fundamentally with Anthropics announcement is apparently "attribution, not copying."
The Mononoke project sits in a facebook org repo, so i assume it's a Meta project.
So I guess my question is, if it's good for one company, why isn't it good for the other company?
I realize real people work at these companies, but I can't feel sympathy.
Sure. But neither should we be impressed with Anthropic for making a big deal out of (let's be perfectly honest) generating an SCM architecture on the backs of other people's ideas.
The company is predominantly FAANG people. They’re going to just rebuild what they know. I don’t think you need any kind of conspiracy here. One year into ad tech and everyone was using HyperLogLog. Everyone was using 20 years ago LMAX-style disruptor, and single threaded event queue powered by loop called governor. It’s just what happens. People carry in their head what they know.
IP maximalism is the present zeitgeist but that’s just how knowledge flows.
It isn’t something I care very much about, except when it’s used as a certificate of achievement. I almost never do literature searches with an attempt to dedupe. I only ever do it to see if someone has explored something better than I have. That’s often the case but other times it is not.
Absolutely not. When I create projects I only credit other existing systems if they are a direct inspiration. If I independently come up with the same idea as someone else I see no reason for me to do the due diligence and credit them.
What happened is that it wasn't a FAANG engineer replicating what they know, rather one asked Claude what to do and it told them to replicate what it knew.
That's how the knowledge that it was a facsimile was lost.
Rebuilding what you know from the previous FAANG you worked at is expected on the whole.
What is douchey is presenting the whole thing as some sort of intense novelty and stroke of genius required in the age of agents when it's just doing what the other BigCo companies did to scale their monorepos already. Like a decade (or more) ago.
The reality it is when I first read the thing I was -- as a Xoogler -- like "Oh, yeah, so, like Piper & SrcFs and the stuff that Meta also does" and really didn't understand why they wouldn't have started with something off the shelf inside of vibe-conjuring a clone that they would then have to support
To me it speaks ill, again, of the engineering culture at Anthropic. "We do these things not because they are useful, but because they are novel."
Don't they have better things to do at Anthropic than building their own source control or rewriting Bun from scratch in another language? Like, y'know, basic site reliability? Or a coding harness that doesn't eat multiple GB of RAM?
I don't expect Scion's design to be very good, and the implementation is likely pretty bad, unless it is a near 1 to 1 copy of existing open source.
The amount of training data for incremental/derived data systems is quite sparse in the grand scheme of things. I've seen little to no improvement over the last year when testing new models in that area, they always make some pretty bad mistakes, and what is correct is very inefficient.
Thanks. Indeed, the Scion design is quite good because Claude was pointed directly to Mononoke and asked to analyze the code base and copy it. I am very proud of what our team built by making contrarian bets at exactly the right spots.
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.
Damn. It’s hard not to see it as plagiarism. I can only imagine the surprised Pikachu face you must have made reading that announcement from Anthropic.
> I think the level of imitation goes well beyond having similar insights.
Uhuh:
> To solve this, we moved the diff-friendly representation to being derived data (i.e. an index).
Coming up with the idea of an index is not a novel thought. Nothing Anthropic described in their post was anything unexpected that one working from first principles that their problem presented would not have come up with.
Except the resemblances extend to the entire server, not just the idea of derived data. The idea of derived data becomes apparent only once you have bought into the core Mononoke insight about Bonsai changesets, later copied wholesale and presented as the core Scion insight about Scion changesets.
As I suspected at the time of writing the post (but could not verify) and as was later confirmed in private correspondence to me, Anthropic did not come up with this from first principles. Claude was pointed directly at Mononoke and asked to re-engineer it.
From the Anthropic announcement:
“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.
If I credit my newly introduced car as inspired by Corvette, then sure, it might be ok not to mention the engine (Mononoke is the server part of Sapling)
However if my new car's engine is a near copy of the one in the Corvette, and my announcement gushes about the engine using the same terms the Corvette design team invented...
Then can you see how a mention might be nice?
Sounds like they did get a mention
3 replies →
It's called "clean room reverse engineering" /s
7 replies →
To me, this sounds like it's less about the technology, whether it's open source or not, and more about the people in the room that are influencing the design, direction, and implementation of it. All of which are very likely to have previous positions at major companies responsible for the products mentioned.
Perhaps if there is any ambiguity, it's intentional on the part of caution around intellectual property provenance.
The level of inspiration goes well beyond "hard-won lessons". Something like Lore (slop design document aside) can claim that level of inspiration. Here the data model is a direct copy, down to the terminology.
To be uncharitable, this is marketing for Anthropic's impending IPO.
I see correlation instead. You IPO when you grow like crazy. You build something like scion when you grow like crazy.
18 replies →
> Here the data model is a direct copy, down to the terminology.
That’s not surprising to me - they designed and built it using their LLMs, of course it’s duplicating prior work. That’s essentially the core of what LLMs do, after all.
Effectively nobody considering buying into the IPO cares about Anthropic's source control system. They could be passing around floppy disks and so long as they were still shipping nobody would care.
9 replies →
Why is that bad?
Mononoke and Sapling are open source systems. Why shouldn't new software take inspiration from how they are designed?
9 replies →
> hard-won lessons in mind
Another Claude-written article
Yea, hard-won, who talks like that... oy vey
> Another Claude-written article
This is the load-bearing seam.
2 replies →
When Fable first released, I had it "one shot" a project using an initial spec and a team of agents. I was blown away with how good the results were.
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.
GitHub is to agents what StackOverflow was to developers back in the day (in a meme kinda way).
More seriously, I'm curious if you checked on the licensing of said codebases, were they permissive or strong copyleft?
Very few licenses allow you to copy code verbatim without acknowledgement.
Lolol nobody is checking that shit. Do most people prompting AIs even understanf what copyleft is?
I think a lot is memory really. For fun you can try pointing just about any model against the older kaggle challenges and it’ll come up with more or less the winning solution from memory. It’s here where you see a Gemma 27b perform about the same as opus 5.5
It's the same for CTF challenges. Many get 'solved' because a writup was found and steps were followed.
I asked it to sketch out something from a research paper, to later find out most of the code was translated from another implementation of the paper.
It is like a vacuum cleaner.
I've always worried about the level of "IP laundering" which is done by LLMs.
While that's not technically the case here (given Mononoke's license) it is still quite negative in my view. We will have fewer people wanting to share ideas openly since LLMs are so good at not only finding them, but also not attributing them. This also leads to a loss in diverse collaboration, which is probably one of the biggest drivers for good software.
Right now there's probably a lot of these "novel" ideas floating around which models can present as their own, but that's raiding our coffers with no inbound future stream.
Is this what is expected of how to cite sources? Because if this is the expectation nobody does it.
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.
To be clear, Mononoke is the server-side part of the Sapling system as deployed at Meta. Scion appears to be very closely inspired by Mononoke.
Sapling does a bit more than cite Mononoke. And Oxide was not involved in Mononoke's development. These are kind of details that would not be expected of a casual user. However, when valuations soar into the trillions, we can expect companies with dedicated writing staff to communicate attribution properly.
*the kind of... sorry, that typo made my answer sound a bit sarcastic which was not the intent.
Anthropic effectively doing a "git clone" with extra steps here. Uncharitable? I don't think so. If this were about functionality, why not use Sapling/Mononoke or extend it and contribute back to the open source community? Because that doesn't juice the IPO valuation.
I think it's worse than just IPO juicing. I think it's "look what our agents can do" and also pushing more on the "software engineers are becoming obsolete" line that Dario public-pronounces. Getting high on their own supply.
Projects seem to be getting approved or pushed there purely on the basis of showing off that they can vibe-build infrastructure.
Which.. yes, you can. But now maintain it. Understand it. Manage thousands of people using it. Those are part of the reasons we re-use proven solutions rather than rolling our own -- not just because the coding part is hard.
Same thing happened with the Bun rewrite. "Oh wow, look what we can do! What's that, nobody adult supervision telling us that this is a bad idea? Let's go!"
The most horrible thing is they don't read their own code. They read the "intent"
On one hand they say AI will end the world. On other hand they say well, we just merge PR by reading the "intent" which I think is the AI summary
git clone would be good. looks more like a peforce evolution tbh
Yet another company is running a bigger-fool scam. They hope idiots will buy their shares during IPO and they wont give a fuck anymore.
I cannot hate them - its rational in its ways. But I hate the idiots who fall for it with each new IPO.
hi rain :) Anthropic’s post reminded me a lot of your work, glad this is getting some visibility. do you think the “time has come” for some of these ideas that previously may not have spread because they need too much learning to appreciate? I wonder what new norms will emerge in creative collectives.
Thanks! Yeah, I think overall several more organizations are going to reach the scale that Meta reached a while ago. I'm not sure if they'll go in the monorepo or polyrepo direction, though; I can see arguments both ways.
Oh wow. Being pretty new to meta and seeing the anthropic announcement I was thinking to myself “wow that sounds a lot like sapling”.
I guess that is the case.
They mentioned Sapling in the post and even hyperlinked it
Whether the ant post amounts to plagiarism, it is definitely somewhere between extremely lazy and intentionally misleading. No particular idea has its inspirations or origins traced or cited, there is no comparison to comparable tooling or discussion of prior work, and there is absolutely nothing to actually position or discuss the project in a manner that might lead to "Contributing to the wider ecosystem."
If only they had had a claude write the post, it'd be full of citations, inspiration credit etc.
I really really wish Sapling could be used externally. It is by-and-large TheWay.
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.
Working for a few years at Facebook, and then returning to the normal world, it was like stepping back in time -- I really think that the mainstream git culture (by which I mostly mean "github") achieved a local maxima around 2012, and has been holding the industry back since :(
(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...)
As someone who came to terms with dying on the mercurial hill, someone who forgot more gitisms than there are to learn in the first place because git cli's inconsistencies and poor taste hurts and neuters my memory, yeah, I relate.
Most people aren't VCS nerds, most are of a generation that only ever knew git. Learning git was a prerequisite they engaged with out of necessity, not by choice, not after exploring the problem space and pondering about different approaches. Learning git was difficult, and the more they learned the more they discovered they had more to learn, including the little things, obscure details and a plethora of paper-cuts. For them (again, I suspect they are a majority), the perspective of learning something else comes with the expectation of a similar daunting effort and steep cognitive reluctance.
That's the paradox of git as I see it: had it been a simple and easy system to pick-up, it would probably have been replaced, and/or the VCS space would be much more competitive.
1 reply →
> [Git/GitHub] achieved a local maxima around 2012, and has been holding the industry back since :(
I agree so hard. It’s inertia is too strong and we’ve stalled progress for a decade.
1 reply →
The startup I work at is working on exactly this. So I agree :)
(Okay not literally exactly, for example, jj/git not hg. But the vibe is the same.)
Hey Steve, I read your recent blogpost on the ERSC site - have you or David (or anyone else at ERSC) felt like there's a Rusty-enough topic around what your startup is doing to give a talk at Rust NYC/Rust conference soon?
There's not really a VCS meetup in NYC, but I got to hear David and others at Rust NYC wax eloquent about Sapling vs Piper and Buck vs Bazel a couple of times, so I think the audience is there!
1 reply →
I am delighted to hear this. Please do not forget support for Windows.
Let me share with you my previous screeds on this topic:
* https://www.forrestthewoods.com/blog/dependencies-belong-in-... * https://www.forrestthewoods.com/blog/using-zig-to-commit-too...
They’re semi-adjacent in that they are about build systems that don’t suck. (buck2 is also mostly TheWay but also not usable outside of Meta and has room for improvement).
Save us from Git and CMake Steve! Please I beg you!!
1 reply →
Agents tend to act differently than humans here. I would have expected most humans to notice and acknowledge the connection. Passing it off as one's own insight definitely feels like plagiarism. Agents are generally not equipped to deal with this type of thing, since looking for prior art is a detour from their goal or an exercise in post-hoc rationalization of knowledge built into the weights.
Whether it is plagiarism or hacking, the buck has to stop with the operators. It's not a good look.
So, if I follow this correctly, Mononoke is a Facebook project. Facebook, now Meta, is widely known to be a company that steals stuff and doesn't give attribution.
The issue, fundamentally with Anthropics announcement is apparently "attribution, not copying."
The Mononoke project sits in a facebook org repo, so i assume it's a Meta project.
So I guess my question is, if it's good for one company, why isn't it good for the other company?
I realize real people work at these companies, but I can't feel sympathy.
Sure. But neither should we be impressed with Anthropic for making a big deal out of (let's be perfectly honest) generating an SCM architecture on the backs of other people's ideas.
The company is predominantly FAANG people. They’re going to just rebuild what they know. I don’t think you need any kind of conspiracy here. One year into ad tech and everyone was using HyperLogLog. Everyone was using 20 years ago LMAX-style disruptor, and single threaded event queue powered by loop called governor. It’s just what happens. People carry in their head what they know.
IP maximalism is the present zeitgeist but that’s just how knowledge flows.
Help me understand. When you write a post about designing a system, do you not do some basic diligence about what existing systems you resemble?
Open source is not IP maximalist by any means. I am merely asking that the appropriate credit be provided.
No. I actually don’t do that and I don’t think that all human work should be O(n) deduplication gated.
Written about it here before: https://wiki.roshangeorge.dev/w/Blog/2026-09-08/Intellectual...
It isn’t something I care very much about, except when it’s used as a certificate of achievement. I almost never do literature searches with an attempt to dedupe. I only ever do it to see if someone has explored something better than I have. That’s often the case but other times it is not.
4 replies →
Absolutely not. When I create projects I only credit other existing systems if they are a direct inspiration. If I independently come up with the same idea as someone else I see no reason for me to do the due diligence and credit them.
4 replies →
What happened is that it wasn't a FAANG engineer replicating what they know, rather one asked Claude what to do and it told them to replicate what it knew.
That's how the knowledge that it was a facsimile was lost.
1 reply →
Rebuilding what you know from the previous FAANG you worked at is expected on the whole.
What is douchey is presenting the whole thing as some sort of intense novelty and stroke of genius required in the age of agents when it's just doing what the other BigCo companies did to scale their monorepos already. Like a decade (or more) ago.
The reality it is when I first read the thing I was -- as a Xoogler -- like "Oh, yeah, so, like Piper & SrcFs and the stuff that Meta also does" and really didn't understand why they wouldn't have started with something off the shelf inside of vibe-conjuring a clone that they would then have to support
To me it speaks ill, again, of the engineering culture at Anthropic. "We do these things not because they are useful, but because they are novel."
Don't they have better things to do at Anthropic than building their own source control or rewriting Bun from scratch in another language? Like, y'know, basic site reliability? Or a coding harness that doesn't eat multiple GB of RAM?
Which off the shelf solution would you have used?
Google's isn't open source. Meta's is an option, any others you would consider?
9 replies →
I don't expect Scion's design to be very good, and the implementation is likely pretty bad, unless it is a near 1 to 1 copy of existing open source.
The amount of training data for incremental/derived data systems is quite sparse in the grand scheme of things. I've seen little to no improvement over the last year when testing new models in that area, they always make some pretty bad mistakes, and what is correct is very inefficient.
Thanks. Indeed, the Scion design is quite good because Claude was pointed directly to Mononoke and asked to analyze the code base and copy it. I am very proud of what our team built by making contrarian bets at exactly the right spots.
Can’t say I have much sympathy for big tech and their employees whining about stolen IP, data and insights.
They’ve been the most egregious offenders as of late
Can anyone explain the difference between sampling vs mononoke?
Edit: I was too lazy. From the README: "Mononoke is the server built for the Sapling Source Control System"
It's a bit complicated:
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.
Woo, I got cited. https://news.ycombinator.com/item?id=50076122
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.
Thanks!
Says a lot about Anthropic given they havent open sourced Scion.
Did they know or did the agents just have that in training data?
Damn. It’s hard not to see it as plagiarism. I can only imagine the surprised Pikachu face you must have made reading that announcement from Anthropic.
Similar to how git was "inspired by" BitKeeper and Monotone?
I do not think Linus has ever claimed that Git wasn't following in the footsteps of those systems.
17 replies →
I thought the Anthropic project did read as a tall order to be completed inside a company from scratch.
This headline is very confusing for fans of Basic Channel / Chain Reaction records.
It is also confusing to fans of Studio Ghibli.
And fans of Toyota.
Monolake, not Mononoke?
Once it's been through the slopotron, the provenance is laundered away.
As a product designer, what do I need to know?
So it's mercurial all the way down, then?
Appreciate the perspective, more to learn from.
> I think the level of imitation goes well beyond having similar insights.
Uhuh:
> To solve this, we moved the diff-friendly representation to being derived data (i.e. an index).
Coming up with the idea of an index is not a novel thought. Nothing Anthropic described in their post was anything unexpected that one working from first principles that their problem presented would not have come up with.
Except the resemblances extend to the entire server, not just the idea of derived data. The idea of derived data becomes apparent only once you have bought into the core Mononoke insight about Bonsai changesets, later copied wholesale and presented as the core Scion insight about Scion changesets.
As I suspected at the time of writing the post (but could not verify) and as was later confirmed in private correspondence to me, Anthropic did not come up with this from first principles. Claude was pointed directly at Mononoke and asked to re-engineer it.
and then what?
Not to be confused with Google's Scion (kubernetes based openclaw platform)
https://googlecloudplatform.github.io/scion/overview/
[dead]
[dead]
[dead]
[flagged]