It turns out the snapshot model is a perfect fit for AI-assisted development. I can iterate freely without thinking about commits or worrying about saving known-good versions.
You can just mess around and make it presentable later, which Git never really let you do nicely.
Plus there’s essentially zero learning curve, since all the models know how to use JJ really well.
How will you ever get the network effects needed to get sustained users with a commercial tool?
Given Git was created because BitKeeper, a commercial tool, pulled their permission for kernel developers to use their tool aren’t we ignoring a lesson there?
We have AI now. AI tools are pretty handy with Git. I've not manually resolved git conflicts in months now. That's more or less a solved problem for me. Mostly codex creates and manages pull requests for me. I also have it manage my GitHub issues on some projects. For some things, I also let it do release management with elaborate checklists, release prep, and driving automation for package deployment via github actions triggered via tags, and then creating the gh release and attaching binaries. In short, I just give a thumbs up and all the right things happen.
To be blunt, I think a SAAS service that tries to make Git nicer to use is a going to be a bit redundant. I don't think AI tools really need that help. Or a git replacement. And people will mostly be delegating whatever it is they still do manually with Git pretty soon. I've made that switch already because I'm an early adopter. And because I'm lazy and it seems AI is more disciplined at following good practices and process than I am.
- It’s from one of GitHub’s cofounders.
- GitHub had a $7.5B exit.
- And the story is: AI is completely changing how software gets built, with plenty of proof points already showing up in the billions in revenue being made from things like Claude Code, Cusor, Codex, etc.
So the pitch is basically: back the team that can build the universal infrastructure for AI and agentic coding.
That said, I find the branding confusing. They say this is what comes after git, but in the name and the overall functionality, seems to just be an abstraction on top of git, not a new source control tool to replace git.
I was really hoping we'd see some competition to Github, but no, this is competition for the likes of the Conductor App. Disappointed, I must say. I am tired of using and waiting for alternatives of, Github.
The diff view in particular makes me rage. CodeMirror has a demo where they render a million lines. Github starts dying when rendering a couple thousand. There are options like Codeberg but the experience is unfortunately even worse.
https://docs.gitbutler.com/cli-guides/cli-tutorial/operation...
and git's reflog:
What I'd would expect of the next vcs is to go beyond vcs of the files, but of the environment so works on my machine™ and configuring your git-hooks and CI becomes a thing of the past.
Do we need an LSP-like abstraction for environments and build systems instead of yet another definitive build system? IDK, my solution so far is sticking to nix, x86_64, and ignoring Windows and Mac, which is obviously not good enough for like 90%+ of devs.
But instead, we get a replacement for Git. And I didn’t even bother to click the link because I’m fine with how Git works. On the list of pain points in my life, “what comes after Git” has roughly the same priority as “try out a more exciting shower gel”. But did you ever step on a LEGO brick while walking to the bathroom at night? That pain is immediately obvious.
Why is nobody solving actual problems anymore?
[0] https://pickupbricks.com
[1] https://www.youtube.com/watch?v=X25MIpQqLIU
This video is from 8 years ago:
https://youtu.be/wXxrmussq4E?si=bgDdDvZODVov3sSC&t=15
I'm sure, by now we could make them for <$1k per robot, if we wanted to.
EDIT: BTW did you see that the page you linked to has this at the bottom of their landing page:
"Example product"
"This area is used to describe your product’s details. Tell customers about the look, feel, and style of your product. Add details on color, materials used, sizing, and where it was made."
so I wonder if they actually sell anything.
I'm not seeing it. When I search for "example" nothing comes up, but maybe I'm looking wrong.
I see it on Amazon as well, with reviews and videos from "customers", so I assume it's not vaporware and that is more an issue with people not filling out the full website template, which is also not a great sign.
https://www.amazon.com/Pick-Up-Bricks-Compatible-Accessories...
I do wonder, though, if it would have been designed differently if the whole “code forge” sort of application (or whatever GitHub and the like are called) was envisioned at the time. Pull requests aren’t even a concept in git proper, right?
It seems like a kind of important type of tool. Even though git is awesome, we don’t need a monoculture.
Generates a pretty email requesting someone to pull commits from your online repository. It's really meant for Linus to pull a whole bunch of already-reviewed changes from a maintainer's integration branch.
The rough equivalent to GitHub's "pull request" is the "patch series", produced by:
Docs: https://git-scm.com/docs/git-format-patchWhich lets you provide a "cover letter" (PR description), and formats each commit as a diff that can be quoted inline in an email reply for code review.
But it took a big brain with a systemic view of the problem and solutions space to bring them all together - in a lighting fast implementation to boot.
GitHub is a social networking site that just so happens to have code hosting related features.
I would argue that it was purposefully designed in contrast against that model.
GitHub is full of git anti patterns.
So the maintainer adds you as a remote and pulls from you.
Because that’s too risky for investors.
"We've replaced due diligence with a DNA test."
"No mutts, no miracles. Three generations of wealth or GTFO."
"Your bloodline is fine. Don't fret the cap table."
"You forgot to attach the pitch deck, but we really like your family crest."
Solving actual problems are hard, and even harder to get money for (see research). Most VC’s are in it for the returns only, not actually making a change, there are some exceptions but they are far and few apart.
I fought for years trying to convince my colleagues to write good commit messages. Now Claude is writing great commit messages but since I'm no longer looking at code - I never see them. I don't think Claude uses them either.
Branches are now irrelevant since all agents work in worktrees by default. But worktrees are awkward since you run out of disk space fast (since we're in a monorepo).
There is a constant discussion ongoing whether we commit our plans or not. Some argue that the whole conversation leading up to the PR should be included (stupid imo).
The game changed completely. It isn't weird that people are wondering if the tools should as well.
Definitely feels like there's opportunity to build something better
What GP wrote sounds like an absolute nightmare of tech debt and unmaintainable spaghetti code that nobody understands anymore to me.
But I guess for some people the increased speed outweighs all other concerns?
"I'm not sure. But at least we got here fast."