HNHacker News
TopNewBestAskShowJobs

pmeunier

672 karma · joined July 13, 2014

submissionscomments
pmeunier··on Pijul is a free and open source (GPL2) distributed version control system
As probably the person in the entire world who has been wanting this for the longest, thank you! Please share on Pijul's Zulip, and ask for any help you may need.
pmeunier··on Pijul is a free and open source (GPL2) distributed version control system
`pijul fork`. There you go, I wrote an entire key-value store just to get that to work. It turned out to be faster than all others, but that wasn't intentional.
pmeunier··on Pijul is a free and open source (GPL2) distributed version control system
- Large/binary files: Pijul splits patches into operations + contents. You can download a patch saying "I added 1Tb there" without downloading any single byte of the 1Tb. No need to add any extra feature.

- Large projects: Pijul solves that easily using commutativity, you can work on partial repos natively, and your changes will commute with changes on other parts of the monorepo.

pmeunier··on Pijul is a free and open source (GPL2) distributed version control system
Pijul does binary files natively, actually. Permissions aren't hard to add, if anybody had a real-world case I'd be happy to help.
pmeunier··on Pijul is a free and open source (GPL2) distributed version control system
Here's game-changing stuff:

- There's an example in the "why Pijul" page of our manual where Git completely reshuffles your lines, and no "custom merge algorithm" could possibly solve it. I would be terrified if I were working on crypto/security code and I knew my VCS was doing that: https://pijul.org/manual/why_pijul.html

- Patch commutation makes all big instances small: no need for submodules, partial/shallow clones, etc. Patch commutation lets you work on a small part of the repo by cloning only the patches you're interested in, and submit patches that mechanically commute with all patches on other parts of the repo.

- Free cherry-picking: no need for strict disciplines, you can just introduce a quick fix on your local work branch, and push just that to production. When you're ready merging the rest, you won't have to solve conflicts again (no need for Git rerere/Jujutsu/…)

- Many uses of branches reduced to "just use patches": many people, especially on fast-moving projects and "early days", don't really know what they're working on, and are dragged onto solving problems they didn't plan initially. Well, Pijul lets you focus on your work, then make patches, and then separate them into branches, thanks to commutativity.

- Separation of contents and operations: this really feels like the CSS3/HTML5 of version control. In Pijul, patches have two "detachable" parts, a part describing what the patch does (as concise as "I introduced 1Tb of data", i.e. just a few bytes), and the contents (not concise: the 1Tb themselves). You don't need the data to apply a patch, so when working on large files, you can record 10 different versions, and your co-workers will only download the parts that are still alive after that. No LFS required!

- Precise modeling of conflicts: conflicts are stored in our model, not "recorded" or "artificially first class". They're literally the core of our model, the initial theoretical motivation. Patches are where you need a good tool the most, and we record them and store your precious resolutions as actual patches, so they don't come back (no "git rerere" needed, and conflict resolutions can be cherry-picked).

Now, we also have less game-changing things like:

- Accurate and super fast "blame" (which we call "credit", and which doesn't require Pijul to look at the entire history like Git does).

- Generic diffs, and therefore merge, i.e. not necessarily line-based. We haven't implemented them, but you could in theory implement AST-based diffs on top of Pijul.

pmeunier··on Popular Git config options
> I would still like to see pijul displace git, but as the years pass the odds of that steadily decrease. Ah well.

Why would that be? Pijul is getting better, simpler and faster all the time.

pmeunier··on Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
This is not true, actually. Pijul answers the question "how to model states so that conflicts are allowed (and hence modeled)", whereas in Darcs it is "how do operational transforms on patches alone inform us about conflicts"?
pmeunier··on jj init – getting serious about replacing Git with Jujutsu
None of pijul's feature have been implemented in Jujutsu. No change commutativity, no associativity, no actual modelling of conflicts. Jujutsu is a better `git rerere`: a good heuristic, but not an algorithm.

Of course if there is an algorithm at some point, it would be really cool to see it described somewhere.

pmeunier··on How Git cherry-pick and revert use 3-way merge
> the problems with associativity that 3-way-merge has, by forcing you to commute through each individual intermediate patch. Like, you don't need Darcs or Pijul if you'll just write some wrapper scripts around Git.

Careful here, associativity is a completely different property from commutativity. Also, Pijul doesn't "commute through each individual intermediate patch" at all, its algorithmic complexity is actually lower than Git's.

pmeunier··on About GitHub’s use of your data
As the author, I do. Pijul is usable, we use it for itself, no problem.

The best forge is still a bit experimental, since we've recently rewritten it using tech that isn't as ready as it promises (looking at you, Cloudflare Workers).

A private repo is 5€/month, plus 0.01€/Gb.day for storage above 100Mb.

And we don't do the kind of stuff discussed here, we're just offering storage and collaboration tools, and intend to keep it this way (as well as open sourcing everything).

pmeunier··on Let's make sure GitHub doesn't become the only option
This is only true for alternatives to Git that are roughly equivalent in terms of complexity and time to learn. This wouldn't hold for an actual improvement (in productivity and training time), just like Rust, Zig or even Go are oven C++ and Java (the industry standards).
pmeunier··on New Pijul Beta Release
Yay, it doesn't seem to be on GitHub either, probably bad, might break my computer.
pmeunier··on Show HN: A version control system based on rsync
Btw, Pijul (https://pijul.org) already does this for binary files and large files. But it also has other advantages such as easier workflows, provably correct merge and cherry-picking.
pmeunier··on Where are my Git UI features from the future?
Another use of rebase is cherry-picking commits, which is also plagued with all sorts of issues. These aren't "bugs", since the issue is that commits aren't really suitable for doing this: patches (like in Pijul or Darcs) do solve this.
pmeunier··on Where are my Git UI features from the future?
Thanks for the kind comments!

I was thinking of doing a synchronous release of 1.0 along with the new Nest: the current one has a cool architecture (replicated over 3 datacenters, using Pijul repos as CRDTs), but doesn't scale well, I'm working on a serverless version. The hard bit is convincing Pijul that it's talking two a real Pijul repo, whereas it's actually talking to a serverless cloud (that's already solved btw).

EDIT: I also don't think there's a "right" way to use Pijul. The magic of algebra means that you can't possibly break the associativity and commutativity properties of Pijul patches, so you can do whatever you want, I'm sure it's fine.

pmeunier··on Where are my Git UI features from the future?
From your usage, do you feel it's 1.0-quality?
pmeunier··on Where are my Git UI features from the future?
I'm one of the main authors. No stagnation, the future is bright but I've been founding a small company recently, not related to Pijul. I've shown an MVP to customers three months ago, now I'm close to 1.0 there. I promise I'll move back to Pijul soon.

Another issue is the Nest (our hosting service), I've been working on a new Nest that can benefit from being open source, unlike the current one.

Another indication that it's doing alright: I'll give a talk about it at BOB 2023 (bobkonf.de), and an invited talk in April at Collège de France.

pmeunier··on Sapling: A new source control system with Git-compatible client
Because it is based on Git, jj is not a CRDT, it seems to be a better merge algorithm (even though the details on their algorithms are scarce).

When I say "not a CRDT" I'm obviously talking about HEAD not being a CRDT, a Git repo is append-only, so the history of a Git repo actually is a CRDT (but that's not what the comment above meant).

pmeunier··on Sapling: A new source control system with Git-compatible client
> A patch-style system (like Pijul) probably makes this easier: if everything is a patch, every patch can be signed atomically.

In Pijul, patch authors are public keys and patches are signed by default. The link with an author's identity is done outside of the patches to allow for changes in name or email address.

pmeunier··on Scaling Git’s garbage collection
I'm just following Rustacean traditions of fixing things from the root.

When you have to write a web browser, you do have to fix C++ before you can actually start. I'm digging a bit deeper by avoiding blackouts so my French servers keep running (the Nest has two other locations), then I'll fix the server code.

pmeunier··on Scaling Git’s garbage collection
This is just the Nest, not Pijul. I'm responsible for that, and sorry about it. I said I'd fix it soon, at the moment I'm working on an app to fix (a small part of) France's electricity crisis. It's mostly done, but it took me a while to write something that would be able to scale to loads of users before the winter.
pmeunier··on Scaling Git’s garbage collection
Pijul handles all merges predictably, by design, because it doesn't actually merge anything, it just applies changes to a CRDT, and CRDTs work.

CRDTs aren't common in real-world distributed applications because they are hard to design. But when the problem is important enough (like in this case) I think the approach is worth it.

One way for Git to do what you said would be to import the repos in Pijul, commit by commit since the last common ancestor, instead of doing a 3-way merge. Technically feasible, but the performance would be terrible.

pmeunier··on Scaling Git’s garbage collection
That doesn't match our experience, have you reported this?
pmeunier··on Scaling Git’s garbage collection
All of the following is described in the Pijul manual:

- Cherry-picking in Pijul actually works.

- Conflicts: you don't need rerere, conflicts don't come back once you've solved them. Conflicts are the most confusing situations, this is where you need a good tool the most.

- So-called "bad merges", where a merge or a rebase goes completely wrong and shuffles your lines around. Git users rarely only call the lack of associativity a "bad merge" and don't look further, but using 3-way merge is the wrong way to merge things, because there isn't enough information to merge correctly in all cases.

- Depending on your pace of work, you might find yourself working on different things at the same time. Pijul allows you to do that without worrying too much about how you'll eventually organise your work. If I worked with Git for example, I'd spend a lot of time organising my branches, they'd never be right, and I'd spend a lot of times rebasing afterwards. Pijul frees me from that work.

- Large files, but Git doesn't treat them well for historical reasons, not for reasons inherent to its design (unlike the other points).

pmeunier··on What comes after Git
I'm one of the authors of Pijul, and I have plans to turn it into a synthesis of snapshots and patches, I've implemented the formats and initial steps, see https://pijul.org/posts/2022-01-07-compressed-sanakirja/

The formats are ready for the next steps, but since this is only useful for really massive repos, I want to wait a little bit before spending the time on these features. If more people start using it, it may provide the motivation needed.

pmeunier··on What comes after Git
Wow, you heard about Pijul years ago then.

I believe it is production-ready, in the sense that there hasn't been any real bug in months. I'll remove the "beta" label when more people use it.

One thing that isn't production-ready is nest.pijul.com, but mostly for lack of funding: that platform uses the CRDT nature of Pijul to replicate all the repositories in different datacenters, but the machines it runs on are somewhat undersized, and the PostgreSQL databases don't like that very much.

But you don't need that to use Pijul, a simple SSH server works fine.

pmeunier··on What comes after Git
Pijul works quite differently from Darcs: the primary datastructure in Darcs is indeed a list of patches, and the main operation is rearrangement.

Pijul is instead a CRDT, meaning that independent patches can be applied in any order without changing the result, which makes rearrangement unnecessary, and the system much faster.

pmeunier··on What comes after Git
> - Git is line-oriented and has no notion of semantic diffs and semantic merges. This makes it a raw tool when working with, ironically, source code.

Compare this with Pijul as well!

I've been working on legit.pijul.com (you can try it, but nothing is ready!), which leverages byte-level storage to get higher-level diffs (I know this sounds counter-intuitive, but finare storage granularity gives you more flexibility to compute diffs).

That said, Git isn't actually line-oriented, 3-way merge is. But then even a byte-oriented 3-way merge would give the same shitty merges as Git.

pmeunier··on Thrussh – Portable SSH client and server library
I'm the original author, and stupidly chose a name I knew was ambiguous (bird/yeast infection). It is a rather dumb joke on the fact that Rust is a fungus as well.

If someone here cares to suggest another name, I'm interested.

pmeunier··on We Put Half a Million Files in One Git Repository, Here’s What We Learned
Just seeing this now. If you look at the conversation, this was fixed within a few hours.
← PreviousPage 2 of 10Next →