Specific commands don't really showcase the appeal of jj. If anything they might scare someone at first glance. It's the fact that the workflows are intuitive and you never find yourself reaching for help to get something done. You really need to try it to understand it.

▲

tomnipotent 8 hours ago | parent | next [-]

> that the workflows are intuitive

It can't be both intuitive and yet too complicated to show examples at the same time.

▲

WesolyKubeczek 8 hours ago | parent | prev [-]

The only intuitive interface is the nipple. All other things are learned.

I feel very comfortable using git. Maybe jj is better, but not seeing is not believing.

▲

baq 8 hours ago | parent | next [-]

jj is better for some workflows, which, if you're a git expert as you claim, you conciously or subconciously avoid as 'too much work' or 'too brittle'.

if you don't care about them after accepting this realization... it's fine. git is good enough.

	▲	ncphillips 8 hours ago \| parent [-]
		I’m not a fit expert by any means. The workflows being described do not appeal to me but not because of the way fit works. They sound confusing and I don’t understand what benefit I’m getting out of them. Like, it’s a solution to a problem I’m not sure exists (for me)

▲

BeetleB 8 hours ago | parent | prev [-]

> but not seeing is not believing.

Classic denying the antecedent :-)

https://en.wikipedia.org/wiki/Denying_the_antecedent

	▲	coldtea 8 hours ago \| parent [-]
		It's not supposed to be a modus ponens deduction. Just an expression of what the Missouri state's nickname says.