pmeunier

8 ms·

31.
by pmeunier 3y ago
- 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: Pi
32.
by pmeunier 3y ago
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.
33.
by pmeunier 3y ago
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 i
34.
by pmeunier 3y ago
> 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.
35.
Pijul (and its storage back end Sanakirja) on the mainframe(pijul.org)
3 points by pmeunier 3y ago|0 comments
36.
by pmeunier 3y ago
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&
37.
by pmeunier 3y ago
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 a
38.
by pmeunier 3y ago
> 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 her
39.
by pmeunier 3y ago
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 Worker
40.
New FaaS and open source design for the Nest, a hosting service for Pijul(pijul.org)
6 points by pmeunier 3y ago|0 comments
41.
by pmeunier 3y ago
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
42.
by pmeunier 4y ago
Yay, it doesn't seem to be on GitHub either, probably bad, might break my computer.
43.
by pmeunier 4y ago
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.
44.
by pmeunier 4y ago
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
45.
by pmeunier 4y ago
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&
46.
by pmeunier 4y ago
From your usage, do you feel it's 1.0-quality?
47.
by pmeunier 4y ago
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 promi
48.
by pmeunier 4y ago
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
49.
by pmeunier 4y ago
> 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 ide
50.
by pmeunier 4y ago
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 server
51.
by pmeunier 4y ago
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
52.
by pmeunier 4y ago
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 de
53.
by pmeunier 4y ago
That doesn't match our experience, have you reported this?
54.
by pmeunier 4y ago
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 situatio
55.
by pmeunier 4y ago
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-sanakir
56.
by pmeunier 4y ago
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 pro
57.
by pmeunier 4y ago
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
58.
by pmeunier 4y ago
> - 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 tr
59.
by pmeunier 4y ago
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
60.
by pmeunier 4y ago
Just seeing this now. If you look at the conversation, this was fixed within a few hours.

More ›