> that the workflows are intuitive
replyIt can't be both intuitive and yet too complicated to show examples at the same time.
The only intuitive interface is the nipple. All other things are learned.
replyI feel very comfortable using git. Maybe jj is better, but not seeing is not believing.
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'.
replyif you don't care about them after accepting this realization... it's fine. git is good enough.
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)
reply> but not seeing is not believing.
replyClassic denying the antecedent :-)
It's not supposed to be a modus ponens deduction.
replyJust an expression of what the Missouri state's nickname says.