I see a future in jj

(steveklabnik.com)

325 points steveklabnik | 2 comments | 22 Oct 25 17:21 UTC | HN request time: 0.453s | source

Show context

oefrha ◴[23 Oct 25 01:16 UTC] No.45677124[source]▶

I gave jj two honest tries. While first class conflicts is a cool idea, in practice I deal with staging/committing 30x more than conflict resolution, and coming from magit, using jj’s hunk split & select felt like being thrown into stone age. Plus I rebase a lot and get a lot of jj’s benefits from magit’s various rebase shortcuts already, IIRC first class conflicts was the only truly novel thing I didn’t have. For people like me who stage/commit often and judiciously I don’t think jj will beat magit until its hunk selection UX comes close.

replies(6): >>45677310 #>>45677775 #>>45678027 #>>45678524 #>>45678766 #>>45679013 #

1. Balinares ◴[23 Oct 25 07:00 UTC] No.45679013[source]▶

>>45677124 #

If you understand why having a great UX on top of bare git is valuable, you have understood 95% of what's to understand about jj.

replies(1): >>45680364 #

2. jbstack ◴[23 Oct 25 10:44 UTC] No.45680364[source]▶

>>45679013 (TP) #

But there are dozens of great UXs on top of Git already, so if that's 95% of what jj is about then you seem to be making an argument for jj adding very little value. My understanding is that jj offers more than just UX enhancements.

↑