More shortcomings of jujutsu:

Some things that are also missing are signing commits and such, but again one can use git for this.

Also, git servers and tools like github, gerrit etc. don’t know about jujutsu’s change ids, so the advantages are kept local. But this is changing, the tools are adding this metadata.

Also, one can sync up jj repos with rsync, which transmits the change ids.

gitk shows many temporary commits which is distracting.

It obsoletes Emacs Magit, which means vim is the better choice for editing commit messages, which means you see yourself morphing into a vim user. Or maybe emacsclient.

Building jujutsu from source requires a fairly up-to-date Rust environment. (One can download a binary that is statically linked with musl from github but I hate downloading binaries). Debian stable has not even an out-dated version. Building it under Guix’s cargo took me some tries.

If you work on a Mainframe or Tandem system, you’ll need to wait until your system’s Rust port is done. A hefty requirement compared to the needs of building git.

Seeing the list of dependencies makes one wonder whether it was written in node/js.