> You certainly don’t need 20 diagrams to understand why you’d want to use jj.

You're talking about Git and jj. Surely, then, you must be a programmer, or at the very least have a passing understanding of programming. Perhaps you would like a refresher on control flow?

"If it takes 20 diagrams to make your case for why jj is better... Git is fine"

  if (jjArticle.Diagrams.Count >= 20) Git = Fine;
  else if (jjArticle.Case == Compelling) Git = NotFine;
  else Git = Fine;

I made an if statement. If the condition of my if statement isn't true, then a different branch is followed.

The article is extremely presumptuous, asserting that the software the reader currently uses is not good enough. I find the article strongly fails to make that case, and a part of why is because anything that takes 20 diagrams to explain is more convoluted than I need, ergo, Git is fine. That doesn't mean jj isn't good. Maybe jj is even better than Git. But the premise of the article isn't convincing the reader that jj is better than Git, but rather than Git is not good enough and that the reader should explicitly go out of their way to stop using it in favour of jj, which is a much stronger case to have to argue. You suggested I'm being judgmental but if anything it is the article that is judgmental.