Maybe it's due to different thinking process. But I can't think of doing a branch without knowing why I would need to do it, which also give me a quick indication of how I should name it. Everything is local anyway so I don't complicate stuff.
│ ○ lrvwrmqv [email protected] 2026-09-07 22:13:12 977b1ab7
│ │ harden running image identity fixtures
│ ○ vqmsmkup [email protected] 2026-09-07 22:13:12 bcd98591
├─╯ add running compiler image identity
◆ mxvotmyz [email protected] 2026-09-07 21:53:55 trunk e37a132e
│ satisfy the byte recovery Clippy gate
It's nicer with color. Anyway, this is an anonymous branch, with two changes on it. "add running compiler image identity" and "harden running image identity fixtures" let me know what that branch is about, without needing to add an extra name onto the branch itself.https://news.ycombinator.com/item?id=50577902
But the relevant bit to this is the following
I want tooling centered around the concept of a patch, not the concept of commits.
Commits for me are settled patches. I don't go around editing commits that much (and I have the tooling to make it trivial). Because for me, the patch inside has served it purpose. When I found a new purpose for it, the context has already been changed, so even when it saved me a bit of typing, I had to look at it anew.So only the few commits around my current tasks are in flux. There's not a lot, so rebasing is very easy, even with the git cli. Same with editing a span of commits. It becomes the workspace and thus can easily be modified. Everything else is just on hold. That's why I like named branch. Because I look at it holistically instead of individual commits.
Maybe your workflow is different, and you are always doing surgical treatment to a complicated tree. But I never needed to do so. These days I'm even leaning towards a single patch for a feature or a fix. Way easier for communication.
EDIT
reply slowed down by HN moderation.
One of the nice things about jj is you don't need to name a branch. You're just working on a graph. When you think you have something consistent and would like to give a name to it, you can do it (before or after the fact). But the lack of friction in creating a temporary new branch is amazing.
If you used VCS before git and loved how easy branching is in git, this is the same feeling in jj, but now with git being the old, tedious way.