I don't think we're going to convince anyone to replace git on speed alone. I don't spend that much time waiting for git operations, even on really big repositories.

This looks like an interesting design, but I kind of just want to wait 3 years and see if some new VC system emerges victorious rather than try out all these new things

QnA-section start with "Is Oak a git alternative for AI coding agents?" How is that a question left unanswered in the text before.

Is this AI slop or a genuine project?

Cursor announced something similar, Origin [0], how does it compare?

[0] https://cursor.com/origin

genuine question: is latency that big of a deal wrt tools for agents? I see this a lot with these AI-native tooling replacement projects, but surely the inference will be orders of magnitudes slower?

From the obviously slop-generated website, to the wild technical inaccuracies like "Git makes you clone the entire history before you can open a single path", to the weird focus on performance when runtime is usually dominated by the LLM, I think I can safely give this a miss. Oh and,

> The commit-message tax.

> Git demands prose on every commit. You burn tokens writing "wip", "fix", and "address review", messages no human will ever read, just to checkpoint your own progress.

Yes, making agents describe their work in a way that is readable to humans and other agents is clearly a bottleneck that must be fixed.

What is this garbage? The only thing I agree with is that worktrees kind of suck (usually once submodules are involved).