Comment by quantummagic
11 hours ago
I love the idea of building a new Git UI on top of Git primitives[1], but the REST inspiration leaves me feeling underwhelmed; there has to be a more human-friendly model.
11 hours ago
I love the idea of building a new Git UI on top of Git primitives[1], but the REST inspiration leaves me feeling underwhelmed; there has to be a more human-friendly model.
The most human-friendly thing is probably natural language. If so, it is LLMs who should have an intuition about the REST interface and its URI syntax. I personally would prefer to glance at it, but not to type it repeatedly. Especially, hashes.
So, the actual question is how to make this machinery un-screw-up-able. (Author)
> the REST inspiration leaves me feeling underwhelmed; there has to be a more human-friendly model.
Jujutsu VCS! https://www.jj-vcs.dev
It doesn't use Git primitives directly, but it has Git interoperability using semantically more powerful primitives. (e.g., there is not only one index -- you can perform rebases, amends, squashes etc. remotely (without checking out first) -- conflicts are non-blocking and support n-way merges -- and so much more)
I've embraced it to the point of porting complex agentic frameworks to support jj (https://github.com/LoganDark/get-shit-done) and I do not regret it at all. Jujutsu is my absolute favorite VCS now.