The key insight in the third sentence?

> ... CRDTs for version control, which is long overdue but hasn’t happened yet

Pijul happened and it has hundreds - perhaps thousands - of hours of real expert developer's toil put in it.

Not that Bram is not one of those, but the post reads like you all know what.

vova_hn2 3 hours ago | parent | next [-]

I have a weird hobby: about once a year I go to the theory page [0] in pijul manual and see if they have fixed the TeX formatting yet.

You would think that if a better, more sound model of storing patches is your whole selling point, you would want to make as easy as possible for people who are interested in the project to actually understand it. It is really weird not to care about the first impression that your manual makes on a curious reader.

Currently, I'm about 6 years into the experiment.

Approximately 2 years in (about 4 years ago), I've actually went to the Pijul Nest and reported [1] the issue. I got an explanation on fixing this issue locally, but weirly enough, the fix still wasn't actually implemented on the public version.

I'll report back in about a year with an update on the experiment.

[0] https://pijul.org/manual/theory.html

[1] https://nest.pijul.com/pijul/manual/discussions/46

	▲	AceJohnny2 2 hours ago \| parent [-]
		> It is really weird not to care about the first impression that your manual makes on a curious reader. On the contrary, I think this is an all-too-familiar pitfall for the, er... technically minded. "I've implemented it in the code. My work here is done. The rest is window dressing."

▲

simonw 4 hours ago | parent | prev | next [-]

I hadn't heard of Pijul. My first search took me to https://github.com/8l/pijul which hasn't been updated in 11 years, but it turns out that's misleading and the official repo at https://nest.pijul.com/pijul/pijul had a commit last month.

... and of course it is, because Pijul uses Pijul for development, not Git and GitHub!

▲

idoubtit 4 hours ago | parent | next [-]

The canonical website is https://pijul.org. The homepage has a link to the pijul source repository.

	▲	ozten 3 hours ago \| parent [-]
		They should mirror on GitHub for marketing purposes

▲

codethief 4 hours ago | parent | prev [-]

> I hadn't heard of Pijul

I'm surprised! Pijul has been discussed here on HN many, many times. My impression is that many people here were hoping that Pijul might eventually become a serious Git contender but these days people seem to be more excited about Jujutsu, likely because migration is much easier.

	▲	simonw 4 hours ago \| parent \| next [-]
		Looks like it makes the homepage only once or twice a year (using points>50 as a proxy for that), had more buzz around five years ago: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
	▲	jedberg 3 hours ago \| parent \| prev [-]
		I too am here all the time and have never heard of it. But it looks interesting.

▲

rbsmith 3 hours ago | parent | prev [-]

Do you use Pijul?

From time to time, I do a 'pijul pull -a' into the pijul source tree, and I get a conflict (no local work on my part). Is there a way to do a tracking update pull? I didn't see one, so I toss the repo and reclone. What works for you in tracking what's going on there?