A Coherent Vision for the Future of Version Control

Re:A Coherent Vision for the Future of Version Control by vova_hn2 on Sunday March 22, 2026 @02:05PM (#47480301)

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

[ Parent | on HN ]

Re:A Coherent Vision for the Future of Version Control by AceJohnny2 on Sunday March 22, 2026 @03:00PM (#47480859)

> 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."

[ Parent | on HN ]

Re:A Coherent Vision for the Future of Version Control by oofbey on Sunday March 22, 2026 @09:54PM (#47484619)

Hilarious. I agree that it says a lot how a project handles reports like these.

[ Parent | on HN ]

Re:A Coherent Vision for the Future of Version Control by onoesworkacct on Sunday March 22, 2026 @10:21PM (#47484799)

I mean, I personally just saw some stuff inside dollar signs and went "huh, weird choice of delimiter"

[ Parent | on HN ]