I am not sure that I understand you correctly. Are you really claiming that lack of speed is why Mercurial did not get traction, and an argument in favor of Jujutsu/jj getting traction?
If you need Jujutsu/jj to get traction among developers for it to become a success, is "engagement", like here on Ycombinator, part of your strategy?
> And for a chain of commits that all have conflicts, chances are fixing the first conflict automatically resolves all other conflicts in the chain, thanks to the auto-rebasing feature. What happens if one is unlucky…
How does it compare to Mercurial? And why would it get more traction than Mercurial?
Do you happen to have or know of any good open source projects on any public platform like GitHub, gitlab or Codeberg, that uses Jujutsu/jj?
Will this have any chance if Jujutsu/jj doesn't get more traction? The effort to learn a new VCS is less than for a programming language, but many developers have not learned git in depth, and Mercurial and others have…
I am not sure that I understand you correctly. Are you really claiming that lack of speed is why Mercurial did not get traction, and an argument in favor of Jujutsu/jj getting traction?
If you need Jujutsu/jj to get traction among developers for it to become a success, is "engagement", like here on Ycombinator, part of your strategy?
> And for a chain of commits that all have conflicts, chances are fixing the first conflict automatically resolves all other conflicts in the chain, thanks to the auto-rebasing feature. What happens if one is unlucky…
How does it compare to Mercurial? And why would it get more traction than Mercurial?
Do you happen to have or know of any good open source projects on any public platform like GitHub, gitlab or Codeberg, that uses Jujutsu/jj?
Will this have any chance if Jujutsu/jj doesn't get more traction? The effort to learn a new VCS is less than for a programming language, but many developers have not learned git in depth, and Mercurial and others have…