←back to thread

I see a future in jj

(steveklabnik.com)
343 points steveklabnik | 1 comments | | HN request time: 0.198s | source
Show context
oefrha ◴[] 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(7): >>45677310 #>>45677775 #>>45678027 #>>45678524 #>>45678766 #>>45679013 #>>45683613 #
baq ◴[] No.45678766[source]
In jj you aren’t supposed to be even thinking about staging and committing, that’s the mental leap required to get what the fuss is about. Everything is a change and you bookmark a parent (or something further out) as the branch head into which you squash or advance the bookmark to a next ready change.
replies(2): >>45678857 #>>45680611 #
1. Hendrikto ◴[] No.45680611[source]
> Everything is a change and you bookmark a parent (or something further out) as the branch head into which you squash or advance the bookmark to a next ready change.

Does not sound any easier or more intuitive than git.