10 comments
Just wanted to note, before I forget, that there is a typo @ https://arialdo.codeberg.page/ju-ju-tsu/preface/at-a-glance....
Impatietn —> Impatient
The book looks well done and a labor of love, but the #1 issue Git users have, merge conflicts, isn't discussed until chapter 13 (reminds me of a Neovim tutorial I read recently where "editing text" isn't until chapter 6).
Wot? You're holding it wrong. With jj you use raw hashes far less than git.
When you start, you use bookmarks mostly because your using as alternate porcelain git and still thinking in terms of git HEAD. Later you will grow comfortable with stacks of changes, and then you will start using change-id's (not SHA1's). Much later, you will learn revset's, and create a few revset aliases of your own, and be moving around the commit tree so fast a git person looking on won't understand what's happening. Then, one day, you will be forced to move back to git, try do to something, and wonder how you every did anything with it and hate every minute you are forced to use it. That's over a year away.
I never, during daily driving, use hashes in git, it's all branch names. If I'm using hashes it's because something went quite wrong and I'm into https://xkcd.com/1597/ territory. Why would I want to move whatever a "revset" is around commits? Doesn't that just... break the point of a commit as a confirmed set of changes?
JJ seems like a thing for people who like managing code vs writing it.
Read the full thread on Hacker News →
Related stories
- Hacker News · 2 points · 5 days ago
- Ju! Ju! Tsuarialdo.codeberg.pageLobsters · 40 points · 9 days ago
- Hacker News · 1 points · 11 days ago
- Qwen Bookqianwenai.comHacker News · 1 points · 9 days ago
- Hacker News · 1 points · 10 days ago
- Hacker News · 1 points · 10 days ago