News for hackers. Stuff that matters.
Re:Jujutsu Primer by danpalmer on Friday November 20, 2026 @01:44AM (#50570993)
I've been using JJ almost exclusively for over 2 years now. It's great, it works fantastically with our rather large monorepo at work.

However I mostly use it backing on to a custom VCS, not git. I can't wait to see some JJ-native forges that don't try to keep it compatible with git, I think there's a lot more benefits and more UX to be explored there!

Re:Jujutsu Primer by ezst on Friday November 20, 2026 @02:08AM (#50571150)
I doubt so, because not being compatible with the git repo format (and therefore requiring distinct hosting, therefore socially excluding from GitHub) is what slowly drove mercurial into obscurity, even though its UX was (and still is) superior to that of git (and JJ, which drew from it), not to mention the other aspects which made hg a much sounder choice on technical merits (e.g. very large monorepos), the users and decision makers both couldn't stand breaking away from the git repo format.
Re:Jujutsu Primer by nvme0n1p1 on Friday November 20, 2026 @02:12AM (#50571183)
Compatibility helps with adoption, but it isn't absolutely required. Git wasn't compatible with the CVS repo format, but still became popular.
Re:Jujutsu Primer by ezst on Friday November 20, 2026 @02:29AM (#50571319)
Sure, but that was before the GitHub monopoly, the social/gamification of it, before the monoculture that ensued, and at a time when it was normal to cruise through the day using 2/3 distinct VCSes (being a FOSS contributor before 2010, you probably would use svn/git/hg/bzr on a daily basis and not need to RTFM for most routine commands like branching, checking in, merging and sharing a diff/series in one form or another).
Re:Jujutsu Primer by danpalmer on Friday November 20, 2026 @02:22AM (#50571277)
I agree that this was a factor in Mercurial dying, but I'm not sure this holds today. Mercurial performed significantly worse than git, that was a factor at the time, but in 2026 the perception is that git doesn't perform well enough (see GitHub outages, GitLab writing on this topic, Anthropic developing their own VCS, etc). Even small teams I know (circa 10 committers) are finding Git to not scale to the speed they're working at now.

JJ has the potential to be a substantial step forward in performance. This will depend on the backend to fully realise it, but a backend that prioritises scalability could vastly outperform git and GitHub's storage.

I think in the post-Microsoft acquisition, post-Dear GitHub letter era, GitHub's shine has worn off. I see a lot more use of GitLab for open source, a lot more use of various other forges. I don't think it's a requirement for a thriving open source project in the way it was for ~2010-2020.

Re:Jujutsu Primer by dotancohen on Friday November 20, 2026 @03:25AM (#50571742)
You conflate Git and GitHub a few times here. I'm a heavy git user, almost never anywhere near GitHub.
Re:Jujutsu Primer by danpalmer on Friday November 20, 2026 @04:55AM (#50572453)
This is somewhat on purpose. For most people GitHub is most of their git experience. But even if it's not, GitHub represents the most mature attempt to scale git storage, and at this point it seems to be clear that it's not doing well at that, at this point it's likely that's not a git problem, but a GitHub problem. The fact that other large companies have migrated off git due to scalability issues is further evidence for that. Git's data model is just not designed for the scale of software engineering happening now.
Re:Jujutsu Primer by dotancohen on Friday November 20, 2026 @07:37AM (#50573847)
Pushing and pulling from a git instance without a working directory on a server is seriously fast and robust.

Try `git init --bare --shared`. You'll never pay for GitHub again.

Re:Jujutsu Primer by ezst on Friday November 20, 2026 @09:35AM (#50575205)
now compare that to just `hg init` for the same effect. Git is so damn powerful!
Re:Jujutsu Primer by eloisant on Friday November 20, 2026 @03:38AM (#50571849)
Mercurial and Git arrived exactly at the same time, in 2005. Most people were using SVN (or some of them still on CVS).

If Mercurial was better than Git it would have won the distributed versioning system war.

I remember Mozilla picking Hg instead of Git to migrate from CVS, and most people were unhappy about it because they prefered git.

Re:Jujutsu Primer by yjftsjthsd-h on Friday November 20, 2026 @03:44AM (#50571900)
I don't think that follows. Even at the same time, social and network effects have impact. Git winning might be as simple as linux using it.
Re:Jujutsu Primer by ezst on Friday November 20, 2026 @03:57AM (#50571994)
not to mention that many at mozilla cried over the loss of mercurial, with some mozillians part-time mercurial contributors rolling-up their sleeves and putting their weight behind jj as a "lesser evil" kind of compromise.
Re:Jujutsu Primer by p_l on Friday November 20, 2026 @04:04AM (#50572033)
Non trivial part was that GitHub had better UX than Hg-supporting forges.

People learnt git to use GitHub

Re:Jujutsu Primer by yjftsjthsd-h on Friday November 20, 2026 @04:06AM (#50572058)
I originally thought to write "Git winning might be as simple as linux and github using it.", before I decided to shorten it:) Yes, I think that was a significant factor.
Re:Jujutsu Primer by letsseeok on Friday November 20, 2026 @05:16AM (#50572637)
We're still on SVN. We exist.
Re:Jujutsu Primer by hobo123 on Friday November 20, 2026 @11:42AM (#50577548)
I remember merges on SVN. It was horrible, and I was so happy when we finally migrated to git. Good riddance.
Re:Jujutsu Primer by DrBazza on Friday November 20, 2026 @08:03AM (#50574127)
Part of the problem was that businesses still wanted a centralized version control system. It's what they understand and need.

At the time there were a couple of low-key Mercurial server solutions: bitbucket, and another I can' quite recall. And then there was Github.

At the time it very much felt like the HN/Silicon Valley hype-cycle/publicity bandwagon jumped on Github. That's really what won 'the war'.

It's a bit like saying, if betamax was better than VHS it would have one the video battles.

Back in the day, Windows was still 'king' and Mercurial was Windows friendly, and git really wasn't, and that still wasn't quite enough.

Re:Jujutsu Primer by BeetleB on Friday November 20, 2026 @10:06AM (#50575689)
> If Mercurial was better than Git it would have won the distributed versioning system war.

Ah, so Windows is better than Linux/UNIX and MacOS. Got it.

Re:Jujutsu Primer by IshKebab on Friday November 20, 2026 @04:38AM (#50572325)
Totally different situation IMO. Git and GitHub were not incumbents at the time. Mercurial mainly lost because it was overall worse than Git, ignoring network effects.
Re:Jujutsu Primer by ezst on Friday November 20, 2026 @06:08AM (#50573046)
You cannot decouple "VCS" (the component at the core of the project collaboration fabric) and "network effects". Too bad we don't have time machines: how many chose git over alternatives because "they've seen others doing it", without putting time and effort to weigh the pros and the cons? My observation is: a substantial amount.
Re:Jujutsu Primer by jon-wood on Friday November 20, 2026 @06:25AM (#50573187)
I'm not too bothered about the backing store but I really want to see some forges gain support for code review based on jj changes rather than git branches and commits. The Github model absolutely sucks if you're someone who likes to keep a coherent history because if you squash the resolution of PR comments into the parent commits nobody can see what changed between when the comments were made and now.

Basing code review on changes and changesets would mean that the evolution of each change could be seen in isolation, which would also mean that you immediately do away with awkward workarounds like PR stacks.

Re:Jujutsu Primer by jkbbwr on Friday November 20, 2026 @10:49AM (#50576508)
Hey I took a crack at this I need to do some updates on it sometime but

https://jjhub.dev/

(I am the author)