We have git.

jujutsu works with git.

git can do everything jujutsu can do (otherwise, jujutsu couldn't work with git).

Thus, jujutsu is a UX / new steering wheel.

ERSC is trying to be a GitHub competitor with what surplus value?

Don't get me wrong, GitHub has a slew of its own problems, but I have not seen any commentary on how ERSC addresses any of the downfalls GitHub has too. We're jumping from one frying pan into another, currently-cooler one?

What about SourceHut? Codeberg? They could offer the same steering wheels.

Edit: Thank you to everyone who replied. The enterprise/teams infrastructure angle makes sense.

For anyone curious the big thing with jj is you can undo. Basically if you were running a rebase and bungled a commit sha or branch name, no worries undo your way out, if you forgot to push but abandoned a commit not issues undo it. Same with all jj commands.

Delta db takes this a step further and everything you edit is a change so your actual edits are also all saved.

I find non destructive-ness for as long as possible approach very nice, since there aren't as many constraints on us not being able to do it nowadays, we had limited storage and stuff in 2000s perhaps but in 2026 even with the killer SSD prices it's fairly cheap to buy more SSD, we can definitely waste 100MB per project storing redundant history we may not ever need.

Same way in photoshop non destructive editing took over, especially useful for humans, but works for AI and LLMs too, they can undo their mistakes as well.

If you haven't tried jj yet, take it for a spin and see how you like it.

It will be good to see what jj will look like with more funded dev work, but I'm always a little worried about financial incentives mixing with the tools I use for the long term. I guess the saving grace is that I don't really need more upgrades to jj or jjui as it stands. I'm pretty much content with the features and so I could just save this copy of the repo for future reference.

As far as large assets goes, I have my own VCS-ish system which I just integrate with jj, but it would be nice to see a non-git backend handle large assets better as well.

Once you start thinking in jj it becomes frustrating having think back to use GitHub as a code repo.

Looking forward to using the VCS stuff you'll create :- )

Is it the animation at the top?

The company is building tools to help organizations manage the exponentially increasing needs

Oh no! Looks like the ram shortage wasn’t enough, SSDs are next! /s