Shameless plug, but a bit related to jj:)
I recently created a project which utilizes FUSE to serve git files directly from object store without a checkout. Main motivation was to sepeedup a worktrees creation (I work on a huge monorepo). In my case it helps a lot - now I wait a second instead of a minute. But then I realised there are other interesting features which having vfs opened:
- tree structure of related branches (simplest case of that are stacked PRs) which rebases itself
- live preview of merge state or any node of such tree
- on demand creation of a new branch which merges any of the existing ones very cheaply (e.g for a throwaway build check)
- quick and simple comand which shows conflicting files between selected worktree and all others
- agents gets notified about such conflicts when they happen
I was able to design it in a way so git sees those virtual workspaces as normal worktrees, and all git commands works exactly as you would expect. So I think for some people, especially on the very big repositpries, it might solve a few problems they try to solve with jj.
https://github.com/pkukielka/gitfold
A few typical use cases: https://github.com/pkukielka/gitfold/blob/main/docs/guide.md
I've been using JJ almost exclusively for over 2 years now. It's great, it works fantastically with our rather large monorepo at work.
However I mostly use it backing on to a custom VCS, not git. I can't wait to see some JJ-native forges that don't try to keep it compatible with git, I think there's a lot more benefits and more UX to be explored there!
I'm fully onboard with the idea that git is horrible to learn and unfriendly for beginners, and also that jj is more convenient and a better UX. I do however struggle to find the point of it for me personally when I've suffered with git for long enough that it has become deeply familiar and very intuitive, and these days I mostly interact with it at a distance through a robot. I've yet to see anything which is for me personally compelling enough to make the effort to switch.
None of the pages explain to me what jujutsu is or why I should choose it over git.
JJ would be interesting to me pre-AI, but these days I don't run VCS commands myself so the problems JJ solves don't apply to me anymore
Is that syntactic suger?
I also strongly recommend this guide https://v5.chriskrycho.com/essays/jj-init/
Does this work well with LLM workflows? Any advantages over git for say Claude or GPT or Gemini to stage changes in a better way?
how does using something like this compare to just using a simple git-wrapper that does all the hard stuff for you (ala lazygit)? Is jujutsu worth learning a whole new workflow for?
What I miss is a guide on how a good commit history should look like, ideally focused on real-world examples.
There's lot's of jujutsu tutorials that teach you how to undo operations and write commit messages before the commit, but almost none cover what to do with all this power.
It's easy to name some general principles like “it should be easy to read” but I don't think it helps, especially if you're a novice like me.
While jujitsu is superior to git in many ways, I found it hard to get Claude and other agents to use it consistently and more effectively than git.
Git and jj work trees are not interoperable, so any tool that assumes git forces you back. Looking at you, Claude app…
jj is great, we use it a lot and we've hijacked it to make a decision-management/context-management system [0]. it's also generally very useful for keeping commit history clean and the squash workflow is good for progressively iterating with ai-written code, since you can squash to preserve the good parts and get agents to build on that.
tried jj once or twice, it just didn't quite click for me. Gitbutler seemed more intuitive, although more than likely less powerful.
I don't really see the point anymore of mastering jj or git; Claude does all the hard stuff for me.
I have made my peace with git.
But I still miss the number commit references from mercurial...
Nice to see a minimal alternative to git.
Also I’m sure there’s a joke in here about rollbacks.
Have anyone tried jj together with gh stack?
Is Domain Expansion planned?
It seems like a good usability upgrade to git but a few years too late. I don't even remember how to use git anymore since the only thing I do manually is pushing to and pulling from the remote repo.
[flagged]
[flagged]
I'm skeptical about the no staging area, but it seems just like a HEAD commit replaces that, which could be nice.
I really don't like the automatic bookmark naming thing.
I'm also skeptical about automatic rebasing, but having conflicts not block the process could be nice, I'll have to try it out on more complex trees.
Also, I didn't see a section on workspaces, but I assume they basically do the right thing.