No, jj is super simple in daily use, in contrast with git that is a constant chore (and any sane person use alias). This include stuff that in git is a total mess of complexity like dealing with rebases. So not judge the tool for this odd case.
No, jj is super simple in daily use, in contrast with git that is a constant chore (and any sane person use alias). This include stuff that in git is a total mess of complexity like dealing with rebases. So not judge the tool for this odd case.
> in contrast with git that is a constant chore (and any sane person use alias)
I don't use aliases, I guess I'm insane?
Also 99.9% of the time, git "just works" for me. If I need to do something special once a year, I can search for it. Like I would with jujutsu.
One rarely needs more from git than `git add -A && git commit -m`.
I rebase stacked diffs all the time so jj makes my life so much easier because its rebasing is much more ergonomic than git.
this seems very easy in git tho how much easier can it get, do you have an example of each of them?
Git rebases don't work if there are conflicts, jj doesn't have this problem. Also idk if you can rebase onto multiple parents with git but jj can do it.
Can you explain how conflicts are not conflicts?
If I change a line of code several times and rebase on to a branch that changed the same lines of code, how are you sure what the right one is?