Any project moves one step at a time, even though the length of time steps might step down over time.
672 karma · joined July 13, 2014
Any project moves one step at a time, even though the length of time steps might step down over time.
That's actually the case, because you can totally simulate Git using Pijul if you want, except for the weird merges where Git shuffles up lines randomly.
> This is a big drawback and so we should hope to get some serious benefits to make up for it.
It is not a drawback at all, there are no downsides to it, and we get the very serious benefit that merges are associative, which is not the case in Git. Indeed, in Git (using diff3 to merge), when Alice adds lines at the beginning of a file and Bob adds lines at the end, some of Bob's line can get merged into Alice's new lines.
> it can not track things like "This calls a function introduced in patch X" which makes the cherry-picking functionality of very little value.
You can totally do that in Pijul by adding extra dependencies, and moreover, this is like saying `git rebase` adds very little value to Git.
> Pijul is like rebase in that it forces you to consider the full history of all the patches in a set which requires to resolve arbitrary conflicts
It is actually the exact opposite: Git forces you to reconsider those conflicts (there's even `git rerere`), whereas Pijul only shows you the unresolved conflicts. Once a conflict is solved in Pijul, it's solved by a patch, and solved forever.
> The finished prototype I built created standard character-based unidiffs, and it sounds like could possibly be slotted directly into Pijul now.
The diff algorithm, acting on lines, is pretty generic in Pijul, but there is a crucial and nontrivial pass after that, to get from a line diff to a graph diff.
A very gentle way of phrasing this ;-) Thank you.
The Nest used to be really fast with the previous Pijul, but I remember the first iteration took a few days of debugging under full load before being stable. I'm not expecting it to be fast until a week or two.
The Nest is still experimental (which explains the downtime), but you shouldn't need to sign in order to view any code there.
> - The project got renamed to Anu. A couple of days ago I tried to visit that page (https://anu.dev), and I wasn't able to find any source code there. I just tried to go there again and the page is offline.
Right, there have been really strong reactions against that move. As a person who carefully listens to HackerNews and Twitter comments for life advice (as one should), I decided to revert that move.
More seriously, I noticed it was distracting from the main point. But then I managed to find another distracting thing, by writing a rant about occurrences of plagiarism that have happened to me, including theft of actual GPL source code, as well as republication of academic papers (in one case, I was fortunate enough to be picked for review).
> - As BlackFingolfin pointed out, the blog post has a "Warning about licenses" at the top. Even though I don't think that's how the GNU GPL works, it's already a big motivator for me to simply close that tab. I do work in the area of data storage myself. Would I want to put myself at legal risk, just because I want to try an experimental VCS?
That is clearly not what I meant, and I'm deeply sorry about this.
> - Why isn't there an official Git mirror of Pijul/Any? Sure, it's awesome if those tools can host themselves, but what about being able to set it up quickly? Pijul/Any is written in Rust. Doesn't Cargo depend on being able to 'git clone' software for it to be installable?
Until there are packages in linux distributions, you can get it with `cargo install pijul --version 1.0.0-alpha`. You would need cargo to compile it from source anyway.
More detail in that blog post, when you have time.
I'm the author, and you just made my day. Thanks.
> On a quick glance, that seems (?) to be the case here
Nope, I don't do crypto, I wouldn't work on other stuff if I did.
That particular file you point to implements decoding from SSH packets, and passes everything on to libsodium.
Second reason: SSH on Windows used to be the most nightmarish thing you can imagine.
That comment of mine doesn't belong in that post, I removed it.
The biggest contribution I got was from someone who rediscovered it independently after asking me about it, and didn't even care to respect the license.
Moreover, the formats of an experimental tool, especially when it is based on new math, need to change frequently. Every single time we've done it in the past, we heard weird comments here, on Reddit and Twitter that our theory would never work because the implementation was not there yet.
There were also unfortunate professional choices I don't want to comment on, which forbade me to work on Pijul other than sometimes on the weekends. I ended up resigning in July 2020, and have worked on the new Pijul more or less 100% since then.
This is due to the lack of a solid theory to match the intuition. The "git way" of trying to match each use case is to add a new command for each new use case.
I don't think you can fix "just the UX" without fixing the underlying algorithms.
Pijul was always advertised as experimental, and Anu is the result of that experiment.
Then that example you link means that you should stop using 3-way merge / git / svn / mercurial.
That is incorrect and is not a conflict.
That's not quite true, for example the mere existence of "git rerere" means that conflicts are not really represented internally.
Also, merges like 3-way merge (the default in Git) are not associative [1], meaning that you might get different results if you pull two consecutive commits A and B from a remote, or if you just pull B.
I didn't say otherwise. However, Google Docs and WOOT are meant to be used "almost synchronously" (which is why I wrote "almost synchronous" in my answer), in the sense that conflicts are presented to the user almost instantly.
By the way, in the paper you mentioned, the words "synchronous" and "real-time" are used to describe WOOT.
This means that we could totally imagine more clever diff algorithms for specific use cases. I don't know anything about PCB design files, but an example application of this is to treat indentation and spaces as their own blocks.
- an "engineering" one, called Sanakirja, which is a fast, forkable, transactionnal, on-disk key-value store. Although it might not be as super-fast as other database engines, it's forkable (allowing to make fast branches in Pijul).
- a few "mathematical" innovations:
- a good understanding of why Darcs is linearly slow in the normal case, and exponentially slow in the worst case.
- some category theory to give a hint of relevant datastructures.
- a few graph algorithms with just the right algorithmic complexity.
- a good enough data representation for patches and repositories.
(disclaimer: I'm the lead author on most of this).Pijul has the potential to do that, since patches provide a very easy interface for doing partial checkouts: - just pull patches related to a particular part of the repository. - don't pull patches related to artwork frequently.
Since Pijul patches always commute, this could work.
Additionally, I hear the new (unreleased) Pijul can split patches between a "transform part" (e.g. "I inserted 2Tb in file f, and deleted 1") and a "contents part" (e.g., "here, have your 2+1Tb: …").