Jujutsu VCS: Introduction and patterns
kubamartin.com
Jujutsu VCS: Introduction and patterns
1–10 of 128 posts
Re: Jujutsu VCS: Introduction and patterns
#2No, I will still not test this, however often it is posted on HN. git works very well thank you.
Re: Jujutsu VCS: Introduction and patterns
#3I think I'm at risk of sounding like a broken record here. I've read about jj many times now but i'm still confused as to what problem it actually solves. I get the same feeling as when some dude wants to sell me on using vim as my primary code editor - arguments are there but it doesn't really solve an issue.
I'll go over to jj when that's the primary tool for the job, or when I can see something that beats the git cli hands down. I'm 100% on the path of least resistance when it comes to tool adoption.
Re: Jujutsu VCS: Introduction and patterns
#4I think I'm at risk of sounding like a broken record here. I've read about jj many times now but i'm still confused as to what problem it actually solves. I get the same feeling as when some dude wants to sell me on using vim as my primary code editor - arguments are there but it doesn't really solve an issue. I'll go over to jj when that's the primary tool for the job, or when I can see something that beats the git…
Well said.
Re: Jujutsu VCS: Introduction and patterns
#5I think I'm at risk of sounding like a broken record here. I've read about jj many times now but i'm still confused as to what problem it actually solves. I get the same feeling as when some dude wants to sell me on using vim as my primary code editor - arguments are there but it doesn't really solve an issue. I'll go over to jj when that's the primary tool for the job, or when I can see something that beats the git…
[deleted]
Re: Jujutsu VCS: Introduction and patterns
#6I think I'm at risk of sounding like a broken record here. I've read about jj many times now but i'm still confused as to what problem it actually solves. I get the same feeling as when some dude wants to sell me on using vim as my primary code editor - arguments are there but it doesn't really solve an issue. I'll go over to jj when that's the primary tool for the job, or when I can see something that beats the git…
So, I've felt pretty much like you - that is, I was happy with git, never really had major problems, and was generally content. Which meant that even though Jujutsu was on my radar for a while, it took me until now to take it for a spin.
In practice, for most bits and purposes, Jujutsu is just designed really well around a core set of primitives, which you use to achieve basically all your use-cases, which in git are spread across many fairly "special-case" features. This means that arbitrary "change tree modification" are pretty trivial.
The easiness of jumping into non-branch-tips and editing them with descendants automatically rebasing is also nice, to me, and fits in well with my workflow. Stacked PRs[0] are much less annoying than in Git thanks to auto-rebase as well.
Finally, I think the "Working on Two Things at the Same Time"[1] pattern is not easy (if even possible?) to achieve with git.
But all in all, as I wrote in the article's conclusion, the reason to use Jujutsu is that it just makes your VCS usage more pleasant, while generally not interfering with anything else as it effectively works as a git frontend.
[0]: https://kubamartin.com/posts/introduction-to-the-jujutsu-vcs...
[1]: https://kubamartin.com/posts/introduction-to-the-jujutsu-vcs...
Re: Jujutsu VCS: Introduction and patterns
#7I think I'm at risk of sounding like a broken record here. I've read about jj many times now but i'm still confused as to what problem it actually solves. I get the same feeling as when some dude wants to sell me on using vim as my primary code editor - arguments are there but it doesn't really solve an issue. I'll go over to jj when that's the primary tool for the job, or when I can see something that beats the git…
Stacked PRs with multi-branch rebases are effortless. Conflicts are actual things in the history that you can come back to later. Everything is automatically committed, so I don't lose work from a bad reset/stash pop.
Maybe these don't help you with your workflow. But in my case these solve the biggest problems I had with git while still being fully compatible.
Re: Jujutsu VCS: Introduction and patterns
#8I think I'm at risk of sounding like a broken record here. I've read about jj many times now but i'm still confused as to what problem it actually solves. I get the same feeling as when some dude wants to sell me on using vim as my primary code editor - arguments are there but it doesn't really solve an issue. I'll go over to jj when that's the primary tool for the job, or when I can see something that beats the git…
I switched from git to jj a few months ago, so I may have some insight.
I used it at work, where everyone used git, and there were 0 issues.
What I really like about it is how changes are sort of soft committed right away and, when I checkout a different branch or change, I don’t need to stash my changes and remember the stack of stashes.
Rebasing and merging feel a little easier, but that might just be because “ours” and “theirs” doesn’t get flipped during rebasing.
I also like the ability to checkout an old commit, make a change to it, then have all my more recent commits automatically get rebased (not exactly what happens, but the analogy works)
All in all, it’s a solid, compatible, incremental step forward in VCS.
The only tangible downside for me is that it doesn’t support git hooks
Re: Jujutsu VCS: Introduction and patterns
#9No, I will still not test this, however often it is posted on HN. git works very well thank you.
That's not a polite response to a hard working person trying to share his endeavor, but I can't say I disagree with you either.
Re: Jujutsu VCS: Introduction and patterns
#10I think I'm at risk of sounding like a broken record here. I've read about jj many times now but i'm still confused as to what problem it actually solves. I get the same feeling as when some dude wants to sell me on using vim as my primary code editor - arguments are there but it doesn't really solve an issue. I'll go over to jj when that's the primary tool for the job, or when I can see something that beats the git…
> when I can see something that beats the git cli hands down.
Then you should switch to jujutsu several months ago.
It's the biggest improvement to my development workflow in over a decade. The last change that was as big was git itself.