this post was submitted on 14 Jul 2025
27 points (90.9% liked)

Programming

22170 readers
57 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

I tried it after using Emacs Magit for about six or seven years, and jujutsu is really easier to use than git and useful if one wants a tidy public history of changes (Linus Torvalds recommendations on that linked here). Plus it is fully compatible to git as backend - other contributors will not even note you are using it.

you are viewing a single comment's thread
view the rest of the comments
[–] Kissaki@programming.dev 3 points 1 month ago

The git compatibility is necessary for adoption and connected use.

jj does significantly reduce the work interface, but the git compatibility increases complexity again.

I tried it out a little bit a few days ago, and found it interesting. But given my git knowledge and tooling, I can't reasonably switch. First, I would miss my TortoiseGit Log view (entrypoint to everything). But also, the connection between jj and git seems complex and potentially error prone.

As a fresh and independent tool I can definitely see how it's much easier and better, especially for people not familiar with Git.