The git history command deserves more attention
- Working with lots of changes in parallel on git can be painful.
- You end up juggling branches and commits, and running scary rebase -i commands that can leave your tree in a half-broken state if you so much as sneeze.jj, an alternative to git, gets discussed a lot these days (1, 2, 3, 4) and is often pitched as a solution.
- While I’m very sold on the problems jj is trying to solve, the way it solves them hasn’t quite hit home with me.
Unverified
- Working with lots of changes in parallel on git can be painful.
- You end up juggling branches and commits, and running scary rebase -i commands that can leave your tree in a half-broken state if you so much as sneeze.jj, an alternative to git, gets discussed a lot these days (1, 2, 3, 4) and is often pitched as a solution.
- While I’m very sold on the problems jj is trying to solve, the way it solves them hasn’t quite hit home with me.
Sources: Lalitm