Developer Voices #
— Solving Gits Pain Points with Jujutsu with Martin von Zweigbergk
Pretty good episode about jj, with its creator, and a little bit of insight into how it is used and developed at google.
I’ll say i think the hard part of learning it is with Git, you’re used to making your changes and then adding them to a commit. With JJ, it’s kind of backwards. You start the commit, add changes to it, and you’re only really finished with that commit when you start the next one. And it’s a small change of workflow, but it’s a big change of ingrained habits and muscle memory. And the payoff doesn’t really come until you try and do your first merge or your first rebase. So if you give JJ a try, and I think you should… Make sure you get past that initial weirdness and get to the good stuff before you really make a decision, because that’s what you want to evaluate.
I’ve started messing around with jj a little bit, and I think it’s worth checking out because it makes rebases and merges and editing history much more simple and easy.
And I’m also excited to see jj in like 3 years. When it has multiple backends, and you can share code and have remotes that aren’t necessarily git. Because the part that’s a little clunky right now is trying to smash jj’s square peg concept of bookmarks into git’s round hole concept of branches. Not that it’s bad. It’s just awkward, and I bet it’s going to get better when there’s a jj native collaboration workflow.