News for hackers. Stuff that matters.
Re:Jujutsu Primer by rootlocus on Friday November 20, 2026 @02:19AM (#50571249)
None of the pages explain to me why jujutsu is or why I should choose it over git.
Re:Jujutsu Primer by duggan on Friday November 20, 2026 @03:19AM (#50571696)
Yeah, never makes it to any list of tools I have a problem with.

Clearly other people are delighted with jj though.

Perhaps the value becomes clear on larger teams, big monorepos?

Re:Jujutsu Primer by LoganDark on Friday November 20, 2026 @04:24AM (#50572218)
> Perhaps the value becomes clear on larger teams, big monorepos?

I find it incredibly useful as an individual contributor opening many PRs on a single upstream project. I can rebase all my PRs onto new upstream changes in one go, I can easily keep the commit graph neat, I can easily squash changes down into specific PRs while keeping my working tree positioned after they all merge together. Really speeds up my workflow, it's awesome. And it's really cool that merge conflicts don't block operations. It's really limiting that git has only one active branch at a time.

Re:Jujutsu Primer by duggan on Friday November 20, 2026 @08:25AM (#50574326)
Interesting! Thanks for the explainer, speed / concurrent development makes sense; that's one area I probably subconsciously steer away from due to the awkwardness.
Re:Jujutsu Primer by skydhash on Friday November 20, 2026 @11:03AM (#50576783)
>> I find it incredibly useful as an individual contributor opening many PRs on a single upstream project

> I probably subconsciously steer away from due to the awkwardness.

I think if I need to rebase a PR enough while waiting for merge that it's a coordination issue and maybe too much churn in the codebase. There shouldn't be a need to do so. Not sure I'd blame git for that.

Re:Jujutsu Primer by LoganDark on Friday November 20, 2026 @11:20AM (#50577089)
I have to be the one to rebase my PR or my signature will become invalid. The only valid way to merge my commits is via fast-forward.

(Do let me know if this has changed, but I've seen any other kind of merge result in the yellow "Unverified" status on GitHub, as I have the thing turned on that requires all commits from me to be signed with my own key.)

Re:Jujutsu Primer by skydhash on Friday November 20, 2026 @12:04PM (#50578001)
That's just the surface concern. Why is the review time so large that you have multiple PRs ongoing? Why is the codebase churning you have conflicting changes that aren't trivial?
Re:Jujutsu Primer by rgoulter on Friday November 20, 2026 @08:06AM (#50574155)
My understanding of jj is that by-default gives you a good VCS workflow that otherwise takes a bit of discipline to use with git.

- e.g. tracks everything by default; this is an advantage compared to "oops I forgot to check it in".

- e.g. reworking feature branches is more natural in jj compared to rebasing in git.

Re:Jujutsu Primer by duggan on Friday November 20, 2026 @08:23AM (#50574303)
Ok, that does help connect the dots.

I expect I've just internalized all these idiosyncrasies after so long.

Re:Jujutsu Primer by rbehrends on Friday November 20, 2026 @07:08AM (#50573602)
The single most compelling reason is probably `jj undo` and `jj redo`, with having a generally more consistent user interface and design being not far behind.

The rest is probably a bit more of a tradeoff for many people in that jj like git also has a non-traditional mental model that you have to learn, with the difference that there is actually rhyme and reason behind jj's. But whether learning that (which can be a non-trivial effort) is worth it to you if you're already accustomed to git idiosyncrasies is a personal decision.