|
|
|
|
|
|
by pmeunier
1260 days 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'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. |
|
|
> 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.
There is a certain time to 'internalize' the concepts of a tool like git or pijul. It took me years with Git and I'm only starting to be confident about my git skills recently. I haven't had that much time with pijul and I haven't absorbed its concepts yet. Despite that, pijul feels like a concept that I can learn much faster. That causes this 'sunken cost' fear. If it was so easy to learn a VC tool, why did I take so much time with Git? That's what I meant with that comment.
I'm a big fan of pijul. I even have a plan in a future project to manage editing history using pijul concepts (or library).