With Git my biggest frustration is having to force-push all the time (and also how you can only get so minute with staging diffs), and since that's because the commit chain is different, the links don't update to refer to the rebased version of that commit (which I guess is fine, but tracking them and providing a link at the top would be nice). Maybe jj kinda has a better system with change-ids but it doesn't play nice with Git web UIs like Forgejo.
Another Git frustration is just how rebasing works in general, which does tie in to the rest. Conflict resolution for me is fine, though I know this is something jj specializes in.
One thing that I really like so far reading about jj is that it has me write the commit message before committing, so that while I'm coding, that guides me. I'm not sure what the jj solution is for when I make various other changes in the pursuit of whatever end goal (fixing bugs I encountered while trying to diagnose another, for example). I'll occasionally go back and want to use those commit messages to find where I made what change, so those need to have commit messages associated with them.
#jj-vcs #jj_vcs #jjvcs #jujutsuvcs #git
