Nobody, including you, have produced an example of a workforce that's substantially easier due to gits model. Either gits design is unnecessarily complex, or t

Nobody, including you, have produced an example of a workforce that's substantially easier due to gits model. Either gits design is unnecessarily complex, or there should be a pay off to the complexity somewhere. Some flavor you can't get, or can't get easily, with jj. I wouldn't need these features either, but I believe teaching jj to beginners will be easier than teaching git. This is further evidence that the problem is git, not the problem space and the need for different workflows: If a different set of concepts serves both power users and beginners better, at what point do we stop pretending that it's all just tradeoffs?