Conversations with JJ

two of my favorite recent engineering products of the past 5 years.. typst and jj

The point about jj having an immature GUI ecosystem compared to git resonates a lot with me; the one time I tried jj I bounced off of it for exactly this reason. VS Code's source control integration is quite convenient for staging selected parts of a file, reviewing the diff, and making commits. For more sophisticated history editing, I've been using GitLens (again in VS Code) for almost as long as I've been programming, and the GUI makes most rebasing fairly seamless. (Conflicts are still a pain, though.)

That said, I am convinced that jj is better designed overall, so I am planning on coming back to it someday!

For anyone else confused/frustrated with the default jj log output, I wrote about how I made a replacement that works better for me:

[revsets]
log = '@ | ancestors(trunk()..(visible_heads() & mine()), 2) | trunk()'

It basically just hides everyone else's branches, leaving only unmerged commits that you have authored.