Very excited to see this come out of Anthropic! This[1] is what we believe over at East River Source Control as well, and seeing one of the big labs talk about it really validates our thesis.

We are offering a bridge to git via a compatibility layer: https://ersc.io/blog/what-comes-after-git

This gives you the ability to ease your transition, as you don't need to swap services and move to something non-git at once. Moving an enterprises' source control is a massive lift, and so building a bridge from here to there is a big focus of what we're doing.

1: That is, if you have a large team + agents working in a monorepo, you will hit git's scaling limits, and need to move to something else. Google and Meta hit this point over a decade ago, but now lots of other companies are too.

▲

schlich 3 hours ago | parent | next [-]

I would love to get an expert's opinion on if Pijul has any potential to be the "non-git backend". Their patch-based data model seems to align with Scion's. And they also happen to already have a functioning forge!

I've done a decent amount of personal research on this but I'm wondering what kinds of considerations go into the storage layer for these things.

▲

steveklabnik 3 hours ago | parent [-]

I apologize for what may come across as a bit of a cop-out answer.

As many of you know, I'm a big fan of jj. The jj project used to have a comparison to Pijul for informational purposes, but the Pijul folks took offense, and so it was removed: https://github.com/jj-vcs/jj/commit/0525dc9d860a5fff6a97d134...

As such, I generally just decline to comment on Pijul, as I want to be respectful of them. As the linked commit says, it's not super clear what exactly they do not like, and so I don't want to accidentally cross some line.

In general I wish the project well, seeing a new VCS in Rust is very cool.

	▲	schlich 3 hours ago \| parent [-]
		It always seemed like it was good tech just in need of good marketing and this seems to confirm some suspicions. But yes, in any case, it's good to be seeing new things! I just want remote storage for my jj repos

▲

rfgplk 3 hours ago | parent | prev | next [-]

Hoping to see where this goes. Have you ever considered working on a semantic VCS? Specifically, where data is classified and tracked/identified by it's contents and not just via the commit hash?

	▲	steveklabnik 2 hours ago \| parent [-]
		Thanks :) I have not personally considered that, no. I'm a bit skeptical of the idea, as you'd need to understand a lot of different things, and at different versions of those things, in high fidelity. But maybe someone will make it work.

▲

esafak 3 hours ago | parent | prev | next [-]

If only we had a jj-native forge to launch all these new backends.

edit: I see they promote jj, but I don't see a forge to go with it.

	▲	ChoosesBarbecue 3 hours ago \| parent \| next [-]
		You might already know this, but in case anyone doesn't, but ERSC's CTO is the creator of jj.
	▲	steveklabnik 3 hours ago \| parent \| prev [-]
		Just to be clear about it, what we're doing is not a forge like GitHub, that is, a large single public platform for social coding. What we are doing is providing reliable infrastructure for the enterprise, initially as a BYOC on-premises option, and possibly a single-tennant SaaS. Keep your eyes peeled and/or use that contact form to hear about it when we're ready, we've been talking with some people for a bit but are going to be opening up more soon. Tangled is doing the social coding thing, and they're jj-native as well. Been a big fan of their work for a while now.

▲

123-as7 3 hours ago | parent | prev [-]

Maybe finish that web page before advertising. There is no real product description.

But hey, if the vibe coding idiots like it, just be vague---it is sufficient.

	▲	steveklabnik 3 hours ago \| parent [-]
		Yep, we've been in stealth for a while! We've only recently started talking more about what we are doing, as we get closer to a general launch. > if the vibe coding idiots like it, The organizations that have these problems are general large enterprises, not vibe coders. Large enterprises are more used to talking to people and do not make decisions solely based on the contents of a web page.