HNHacker News
TopNewBestAskShowJobs

pmeunier

672 karma · joined July 13, 2014

submissionscomments
pmeunier··on Pijul is asking contributors to sign CLA
Not sure why this is news (and the title is misleading: this is for Libpijul only, not Pijul nor Sanakirja).

This has had 0 impact on contributions so far, since "signing" here just means including a patch as a dependency. In 100% of the cases so far.

Also, Libpijul is probably the last place you'd start if you wanted to contribute to Pijul. And since Pijul is GPL-2 and has no CLA, this means there's nothing hidden.

pmeunier··on Conflict-Free Replicated Data Types (CRDT)
There are so many ways to ask for help about that:

- https://pijul.zulipchat.com

- https://discourse.pijul.org

- https://nest.pijul.com/pijul/pijul/discussions/new if the failure is in Pijul itself and not in one of its dependencies.

And even on Twitter (@pijul_org)!

pmeunier··on Write plain text files
Hint: rerere doesn't always work. It's still guesswork, like the rest of merges/rebases/cherry-picking in Git. This is because looking only at the tips of branches doesn't work, and that's the only thing Git can do (with or without diff3 as the merge algorithm).
pmeunier··on Write plain text files
> However, I feel that version control focused on text breaks,

Pijul doesn't, by the way, the diff algorithm is customisable. I wrote one industrial application of Pijul that uses spaces as breaks, and semantics-aware breaking is totally doable.

pmeunier··on Pijul 1.0 Beta
You can use branches in Pijul if you want, but you can't use patch commutation in Git.
pmeunier··on Pijul 1.0 Beta
1. My comment about merges was not on performance. Performance can be considered no correct algorithms, not guesswork (such as 3-way merge).

2. "Git is fast", but when getting into the details, all the operations that are faster in Pijul do not matter.

pmeunier··on Pijul 1.0 Beta
Practical implications: merges are 100% predictable and deterministic, this isn't always the case in Git, sometimes lines are shuffled around (look for "associativity" in the manual).

Also, you can actually cherry-pick.

And rebases are not a hack.

pmeunier··on Pijul 1.0 Beta
The irony here is that I'm the main author of Pijul, and I don't have a driving license.
pmeunier··on Pijul 1.0 Beta
It is fast for some operations indeed. But its merge is not always correct (conflicts might reappear, lines might get shuffled around randomly), and rebase and blame aren't super fast (Pijul isn't as optimised for speed as Git, yet Pijul credit is faster than Git blame, and apply is faster than the diff-and-replay strategy of Git rebase).
pmeunier··on Pijul 1.0 Beta
Well, even Gitflow, while not being unreasonable, wastes engineering time. Most devs know it, so at least they don't have to relearn when onboarding, but then their VCS shapes the way they organise their work, when it should be the opposite.
pmeunier··on Pijul 1.0 Beta
Thanks, but our problem is different, the datastructure on which all of this is based is memory-mapped, and does need some filesystem and OS cooperation to work well.

I haven't tested Pijul on Windows much, and I know that at least at some point it didn't work on WSL.

pmeunier··on Pijul 1.0 Beta
Storage is not really the issue here. If you merely think about snapshots, all this is fine.

The problem come when you merge and rebase your snapshots, possibly solving conflicts in the process. Then none of this snapshot thinking makes sense.

And actually, Git knows that well, since its default merge algorithm diffs the tips of branches with the youngest common ancestor. And rebase "replays" diffs (how would you "replay" snapshots?).

pmeunier··on Pijul 1.0 Beta
You're not the only one, I too like it. But there comes a time when you want your merges and rebases to work predictably (absolutely never reshuffling your lines randomly), your conflicts to be solved once and for all (without hacks like rerere!).

Maybe you may also want your tool to serve your workflows and not the opposite.

pmeunier··on Pijul 1.0 Beta
> How do you avoid the OS randomly deciding to write a page to disk, per https://db.cs.cmu.edu/mmap-cidr2022/ ?

I don't, the OS can flush anything it wants at any time.

pmeunier··on Pijul 1.0 Beta
> I don't think GP was trying to make a strawman

Potential doesn't mean intentional! Sometimes just a lack of precision causes one to argue against a point that was never made (such as "porcelain is the problem").

pmeunier··on Pijul 1.0 Beta
Thanks! I don't have much experience with Windows, and the backend is quite closely tied to the OS.

Is this on plain Windows, or on WSL?

pmeunier··on Pijul 1.0 Beta
Can't clone it. How many files are there? Also, how did you install Pijul?
pmeunier··on Pijul 1.0 Beta
How did you install Pijul btw?
pmeunier··on Pijul 1.0 Beta
The goal of a beta version is to collect feedback, so thanks for that. However, that particular command worked in all the repositories I tried, so I'm really curious about what you are doing.
pmeunier··on Pijul 1.0 Beta
Interested in seeing that repository, is it public?

Never seen that even on massive repositories. `pijul add` times are most of the time comparable with `git add`.

pmeunier··on Pijul 1.0 Beta
Fully solo: no.

Mostly solo: if that means you're in small teams, yes, since you don't need to follow the rigid workflows that prevent large companies from running into Git's problems.

pmeunier··on Pijul 1.0 Beta
> They solve the problem of "pin a specific version of some external 3rd-party repo" really nicely.

My understanding is that they sound to many users like you could do more with them, such as making your repository modular, where in fact if you do that, you run into all sorts of problems.

pmeunier··on Pijul 1.0 Beta
Context: I'm the main author of Pijul, and also a big fan of Git.

This sounds like a potential strawman argument to me, so let's be clear about the complaints you've heard, and my complaints against Git (which, again, I love and admire as the most elegant design I've ever seen for a tool like that).

Mine are not at all in the porcelain, but in the plumbing. My specific complaints are:

- Merges in Git don't have enough information to do the job, and the optimisation problem it tries to solve is underspecified, regardless of which merge algorithm it uses (3-way merge or other): sometimes, there are multiple solutions, and Git ends up choosing a random one. This breaks a fundamental expectation on merges called associativity.

- Solving conflicts doesn't really solve them, it just records a version without the conflict. This can waste engineering time in two ways: either because you need to think deeply about the tool when solving the conflict (and use `git rerere`), or you need to follow a strict workflow, making your work methodology serve the tool rather than the opposite.

- Similarly, rebasing is operational transform. It works most of the time, but not always, and is quite clunky and hackish. Pijul fixes that by using a datastructure that happens to be a CRDT for that part.

In my opinion, all the porcelain issues and the proliferation of unintelligible commands comes from these basic shortcomings in the plumbing.

pmeunier··on Pijul 1.0 Beta
Sanakirja has atomic commits, the only hypothesis is that just a few bytes can be written to disk atomically (I don't remember, but certainly at most 8 bytes).

All writes are done in atomic transactions.

pmeunier··on Pijul 1.0 Beta
> Are there other architectural reasons it's particularly suited to pijul?

Yes, I originally wrote it because I wanted to fork tables without copying any byte. This is how channels (similar to Git branches) are implemented in Pijul.

> I wonder how closely tied together the two codebases are on a practical level.

Pijul can use a generic backend, although in practice only variants of Sanakirja have been implemented. Sanakirja is generic enough to handle different workflows, although large values aren't implemented yet (they aren't hard to implement, I just never needed them and nobody else did it).

pmeunier··on Pijul 1.0 Beta
Many of these blog posts have been on HN frontpage a number of times already, sometimes for quite a few hours… But alright, never at this rate!
pmeunier··on Pijul 1.0 Beta
Sanakirja does all those things indeed: Sanakirja doesn't parse anything, doesn't call read().

The answer to all your other questions is yes.

pmeunier··on Pijul 1.0 Beta
Nothing. However, one could use a central server holding locks on identifiers from the distributed copies.

Not mathematically elegant, but fast and convenient in some cases.

pmeunier··on Pijul 1.0 Beta
That was obviously the first idea, but it isn't really possible. Git is meant to prevent commutation of patches, while Pijul is design to maximise it.

Two-way conversion is still a goal, though.

pmeunier··on Pijul 1.0 Beta
No particular reason, just a mistake in the links. Thanks!
← PreviousPage 3 of 10Next →