[dead]
Who says it's too complex to have multiple implementations? It's under an open source license notably unlike BitKeeper, what's the problem?
The creator of Jujutsu has joined ERSC
191–200 of 282 posts
Re: The creator of Jujutsu has joined ERSC
#192Earlier quoted context omitted.
> I'd argue that the reason a lot of developers have not learned git in depth is because it's actually kind of terrible from a UX standpoint Not really. I remember my early years with git and the favt was that I never needed more than clone, add, commit, pull and push. While I’ve done some mistakes that got ne to learn more, especially with creating branches and undoing. I’ve never needed a lot, even when I started u…
But what if you didn’t have to read a 400-page book to properly version control your software?
I read many 400 pages books to learn various things about software development. So one more to learn about version control was worth it.
Re: The creator of Jujutsu has joined ERSC
#193Earlier quoted context omitted.
> I'd argue that the reason a lot of developers have not learned git in depth is because it's actually kind of terrible from a UX standpoint Not really. I remember my early years with git and the favt was that I never needed more than clone, add, commit, pull and push. While I’ve done some mistakes that got ne to learn more, especially with creating branches and undoing. I’ve never needed a lot, even when I started u…
I honestly kind of think your experience is in favor of the GP’s assessment.
Not really. Learning the piano and learning music theory is two different things but tied together. One is skill and muscle memory, the other is theory and understanding. It’s the same with git and version control. One is a process and the other is a tool.
Re: The creator of Jujutsu has joined ERSC
#194[dead]
Who says it's too complex to have multiple implementations? It's under an open source license notably unlike BitKeeper, what's the problem?
Git had a very small initial implementation, while jj is under development for years and is large. If jj is not too complex to have multiple implementations, why have new implementations not sprung up by now? Is it the Google CLA, or are too few people using jj, or is jj too complex, or some mixture of all of the above?
The Google CLA is still required as of 2026, which I find strange. https://lwn.net/Articles/958805/
> Second, I thought about contributing a fix to that table, and then I saw the contributing requirements:
> > Contributor License Agreement
> Nope, not happening. Nobody should adopt this until it's been freed from that requirement, either by getting the project to remove it or by establishing a version of the project that takes contributions without that requirement.
Re: The creator of Jujutsu has joined ERSC
#195[dead]
Who says it's too complex to have multiple implementations? It's under an open source license notably unlike BitKeeper, what's the problem?
> There is a mandatory CLA you must agree to. Importantly, it does not transfer copyright ownership to Google or anyone else; it simply gives us the right to safely redistribute and use your changes.
[Emphasis from the source]
Does this make it possible for the jj organization to make the implementation closed-source and proprietary, and abandon the open source version, taking all the contributed changes from volunteers and other organizations with them?
Re: The creator of Jujutsu has joined ERSC
#196Earlier quoted context omitted.
The enterprise sounds accurate. You mention performance issues with Git, but there are performance issues with this blog post.
If the worst thing you can say about a git hosting provider is that the performance of their blog is worse than the performance of their git servers, I think they're probably doing an okay job.
> the worst thing you can say about a git hosting provider is that the performance of their blog is worse than the performance of their git servers
No one has agreed to this premise. You have invented it out of nowhere.
Re: The creator of Jujutsu has joined ERSC
#197Why does OpenText (webshield) block this website?
Re: The creator of Jujutsu has joined ERSC
#198Earlier quoted context omitted.
A few advantages for me, even for the same 5 commands I use over and over: - undo - shuffling commits around with squash, split, and rebase is much better than git’s interactive rebase - make commits without having to come up with a branch name (I might make three versions of the same change in parallel to see how they compare) I see git is working on adding some of this under the history command. The revset language…
> - shuffling commits around with squash, split, and rebase is much better than git’s interactive rebase Can you explain this to me? I feel like Git is pretty easy there. - select oldest commit to modify - move the commits around with a mouse or the cursor - close the editor to apply Sure, the first step can go away (which is what they do with git history), but the rest seems pretty optimal to me. Alternatively I can…
It does take a few days to stop missing interactive rebase.
But say you’re in the middle of working on something and you wish you had a commit you made last week on an experimental branch on the current branch before the last commit you made. That’s jj rebase -r oldercommit --before @-, without interrupting your work. I don’t like to think about how I’d do that with git.
Re: The creator of Jujutsu has joined ERSC
#199Earlier quoted context omitted.
I'd argue that the reason a lot of developers have not learned git in depth is because it's actually kind of terrible from a UX standpoint (lots of inconsistent naming of things and somewhat leaky abstractions), and that Mercurial faced an uphill battle in large part because it lacked compatibility with what people were already using. I haven't used Mercurial, but from what I've heard quite a lot of how jj does thing…
As a Mercurial fanboy, git took off thanks to being from Linus, and a requirement to contribute to the Linux kernel, from there the adoption wind was in motion.
As someone who was a mercurial fanboy too, critical element was that Github happpened for git while mercurial had nothing comparable - and before anyone points at bitbucket, it fucking sucked in UX
Re: The creator of Jujutsu has joined ERSC
#200> The company is building tools to help organizations manage the exponentially increasing needs
Oh no! Looks like the ram shortage wasn’t enough, SSDs are next! /s