20 ms·
Pijul – A free and open source distributed version control system
- adekok 10y agoHow does this compare to darcs? http://darcs.net/ http://darcs.net/ Edit: they have some minor text on how it's better, but a more detailed description would be appreciated.
- deleted 10y ago[deleted]
- pygy_ 10y agoNot sure why this was downvoted, it is a legitimate question. https://pijul.org/faq.html#did-you-solve-the-exponential-merge-problem-darcs-has https://pijul.org/faq.html#did-you-solve-the-exponential-mer... answers it, at least partially. There may be a more comprehensive comparison, though.
- adekok 10y agoI looked through the site, and saw some high-level comparisons, but there's not much meat to it. Where Darcs has this: https://en.wikibooks.org/wiki/Understanding_Darcs/Patch_theory https://en.wikibooks.org/wiki/Understanding_Darcs/Patch_theo... Pijul has some text saying "we're better than Darcs in these areas".
- tupshin 10y agoIt is heavily inspired by Darcs, and is based on an alternative "theory of patches" that reportedly has much better worst-case performance characteristics. It is written in Rust, instead of Haskell, also contributing to better/more predictable performance. The Darcs folks are very aware and supportive of it, and last I heard, Darcs might add support for the Pijul patch format. This is an extremely exciting project. (speaking as a long time Darcs fan and passive onlooker who saw the Pijul presentation at rustconf)
- agumonkey 10y agoI find it very uplifting to see both team exchanging so nicely. Feels like good research and progress.
- kreetx 10y agoIt's supposedly faster, or, has a tolerable performance (I've nevere used Pijul, and never used darcs to the extent that it became slow).
- giancarlostoro 10y agoLooks like this is inspired by Darcs but was originally an attempt to improve it for those curious about it as I was. It is written in Rust which gives it all of the benefits (and weaknesses(?)) of Rust.
- zellyn 10y agoSadly, I'm afraid the AGPL license is going to make this untouchable to businesses… :-( [Edit] Interestingly, they cover that. I suppose if you're just running Pijul rather than integrating with its code, it might be safe to use in a corporate environment. Still, it's likely to be offputting.
- mirekrusin 10y agoI may be wrong but I think some (most? all?) companies that are blacklisting agpl3 won't bother going into small print details, license alone is a no-go, no?
- kibwen 10y agoAny company blacklisting AGPL is going to be blacklisting GPL as well, which would preclude using git as well (even the more permissive libgit2 is just GPL with a linking exception).
- skybrian 10y agoThat doesn't seem to be the case in practice?
- CJefferson 10y agoThat's not true, I know several companies happy with GPL, and not AGPL. The thing they worry about is deciding what falls under AGPL. With GPL it is easy, if an executable leaves the building, source goes with it. With AGPL, when almost very thing is web connected, it can be hard to draw the line on what you have to open source (or just tell people you are using.. do I have to add every AGPL program in an Ubuntu server install, just in case one is getting used by something else?)
- tupshin 10y agoCan confirm that this is absolutely not the case. I have encountered a number of companies that are absolutely fine with [L]GPL but not going to consider AGPL. Whether rightly or not, https://www.theregister.co.uk/2011/03/31/google_on_open_source_licenses/ https://www.theregister.co.uk/2011/03/31/google_on_open_sour... and other writings on the topic had a big impact on enterprise adoption of AGPL software. There's also the fact that most prominent AGPL licensing tends to be around commercially backed software where the main backer owns all the source and is therefore in position to not hold themselves to the same standard of sharing changes as their customers and third parties must do.
- baq 10y agoAGPL3 sounds like a death sentence given recent RethinkDB struggles, which is just sad, because the project looks very cool.
- 3825 10y agoAny sources behind the claim that agpl is behind the lack of success for rethinkdb? I am very bullish about agpl. As far as I understand, the choice of agpl has no effect on your code which you put in a repository. Is that not the case?
- scotu 10y agoAs I wrote in another comment here I'm really surprised by the shallow reasoning of fellow developers regarding AGPL: https://news.ycombinator.com/item?id=13643645 https://news.ycombinator.com/item?id=13643645 I mean, I might not understand the finer legal details but thinking "all your code you see after using anything GPL has to be GPL" is really weird, did this people ever used a linux kernel? (yes I know GPL is different from AGPL and at a high level I also know what is different)
- fadzlan 10y agoHonest question, although on a bit different topic I guess. Does AGPL prevents some company creating Github like services for Pijul?
- kibwen 10y agoIt does not prevent any company from creating a Pijulhub. However, if you make modifications to Pijul or link it as a library into other code, that code must be made open-source. (And note that GitHub doesn't even use the original git written by Linus, they wrote their own implementation, libgit2.)
- qznc 10y agoAfaik libgit2 is a derivative of git. Anyways, for Pijul to be successful, there must be something like PijulHub. The bar is higher now. Thus, make it easy to build this hub!
- Kiro 10y agoWhy don't I ever see CC on OSS? Always these complicated licenses.
- l2dy 10y agohttps://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software https://creativecommons.org/faq/#can-i-apply-a-creative-comm... > Unlike software-specific licenses, CC licenses do not contain specific terms about the distribution of source code, which is often important to ensuring the free reuse and modifiability of software. Many software licenses also address patent rights, which are important to software but may not be applicable to other copyrightable works. Additionally, our licenses are currently not compatible with the major software licenses, so it would be difficult to integrate CC-licensed work with other free software. Existing software licenses were designed specifically for use with software and offer a similar set of rights to the Creative Commons licenses.
- deleted 10y ago[deleted]
- scotu 10y agojust to understand, have you ever read the BSD license or the MIT license? Both very prevalent in OSS https://opensource.org/licenses/MIT https://opensource.org/licenses/MIT
- mirekrusin 10y agoIs there any sound reason to use AGPL3 license in this case? Is it to avoid private, non-public modifications by some future pijulhub.com? Something, somewhere feels irrational in my head, especially when I think about popular projects like SQLite which seem to be doing just fine without the whole license thing.
- ue_ 10y agoThe case is simply that the authors probably have a different view of licensing, and wish that their code remains free software even when integrated in other products. It probably wouldn't help that much in the case of something like Github because Github uses their own version of git. Depending on the outlook, AGPL is simply there to fix a loophole in the GPL, and rightly so.
- mhd 10y ago"Because Pijul is based on a mathematical model of collaborative edition, its behavior matches intution, every time." That's not how math and/or intuition works.
- lliamander 10y agoIndeed, but if can accurately deduce what the behavior will be from a few relatively simple rules, then that is an excellent basis for forming an intuition.
- falsedan 10y agoThat's a deduction… intuition is usually drawing conclusions based on pattern-matching on similar situations (e.g. 'how do I do this in git/svn?').
- lliamander 10y agoA fair distinction, but I'm not claiming that deduction and intuition are the same. Rather, I'm saying it is easier to change the patterns you expect if the new patterns are simple and regular. If by intuitive we mean "matches the patterns that other people expect (e.g. git/svn)" then obviously Pijul is not intuitive. But if once one learns the basics, it becomes fairly easy to infer what the tool will do in more advanced cases, then one might say it is at least "intuitable".
- cstrahan 10y agoMath itself isn't necessarily intuitive in every case, but I think their point is this: if their system follows the simplest (i.e. most general) mathematical model, things will be more intuitive (i.e. more special cases == more difficult to reason about). Let's look at example from math: integers and addition. Addition is pretty general -- there aren't, say, weird special cases when one operand is even, or the current date during calculation is Friday the 13th. Addition is associative and commutative, so I can evaluate a long summation in any order I want, or I could chunk up the calculation and have multiple computers evaluate parts thereof, all without any coordination/locking. It's easy to reason about, because the rules are so general, and generalization is what math is all about. Now let's look at software: packaging. What are the semantics for package installation for your language/OS? If you install package A and then B, do you end up with the same result as you would by installing B and then A (i.e. is installation commutative)? Many (if not most) package managers can only support one installed version of a package at a time, and thus installation can not be commutative: installing a package will pull in dependencies that will influence package constraint resolution in subsequent installations, so order does matter. Now you have to be careful not to fuck that up when you set up your cluster's configuration management (or, hell, just get what you need installed on your laptop so you can work on a new assigned project). Now, if the package manager in question supported multiple installed versions of a given package (and had a way of "activating" only a subset of all packages for a given project/application), installation would be commutative, freeing you of the burden of installing things just the right way and in just the right order. This is how Nix (OS pkg manager) and the latest Cabal (Haskell pkg manager) work. So, yes, coming up with a simple, consistent mathematical model for the semantics of your target system will definitely make things more intuitive. It's precisely because most developers are terrible at mathematical reasoning that so much software is so difficult to reason about -- there are tons of unnecessary special cases, when hidden inside all the tangled logic there's secretly a simple set of axioms and theorems that lend themselves to intuitive composition.
- gozzoo 10y agoHow does this compare to git?
- lvh 10y agoGit (and mercurial, and a few others) are snapshot-based. That means that they think of the world as states, with changes between them. Darcs, and pijul, are patch-based. That means that they think of the world as an ordering of patches. Patches aren't the same as commits: commit orderings, for example, are fixed, whereas patch orderings are computed. They can change when you e..g merge a "branch". Branching is similarly "simpler": a branch is just a collection of patches, not just a single commit with an implicit DAG attached to it.
- jdbernard 10y agoGit stores diffs, not snapshots. A commit is a changeset, literally a patch that you can export with `git diff`. Ordering of is layered on top of that and informs things like merges. Can you explain a little more what you mean?
- qznc 10y agoGit does store snapshots, not diffs. Look into the files in .git/objects/* ;)
- deleted 10y ago[deleted]
- tghw 10y agoNot sure why you're getting downvoted, you're describing git correctly. If anyone is questioning this, just play with `git rebase -i [some old changeset id]` and you'll see that it's just an ordering of patches.
- lvh 10y agogit rebase -i does not demonstrate that gits internal model involves a DAG of snapshots (objects); it only demonstrates that git is sometimes willing to move the contents of one of those snapshots around to create a new snapshot. That is very different from a patches-always model, as I have illustrated in a sibling comment with an example link.
- gpm 10y agoHopefully they release "workable pijul" soon (they said on January 10th that they were almost there) [0], they haven't updated the source in the darcs repository June 1st. [0] https://pijul.org/2017/01/10/first-working-pijul.html https://pijul.org/2017/01/10/first-working-pijul.html
- aratno 10y agoWould love to see more explanation (with diagrams) of their patching model. Right now I'm not convinced it has any intuitive advantage.
- tupshin 10y agoThis might be deeper than you are looking for, but this is the theory it's based on, and even has diagrams. :) https://arxiv.org/abs/1311.3903 https://arxiv.org/abs/1311.3903
- vesinisa 10y agoHere is one concrete example compared to git I found digging around: https://tahoe-lafs.org/~zooko/badmerge/simple.html https://tahoe-lafs.org/~zooko/badmerge/simple.html
- krupan 10y agoFor anyone following along still, I just tried the bad merge example that vesinisia linked to with both git and mercurial. Git does indeed do the wrong thing as illustrated on that web page. Mercurial gets it right. UPDATE: both git and mercurial get the concrete version wrong (https://tahoe-lafs.org/~zooko/badmerge/concrete-good-semantics.html https://tahoe-lafs.org/~zooko/badmerge/concrete-good-semanti...)
- rhabarba 10y agoLast time I checked, the Darcs project had mostly fixed the performance issues. Shouldn't it be better to concentrate and unite their efforts?
- WorldMaker 10y agoThis isn't the first time that an entirely different patch algebra has been tested outside of darcs itself (camp is mentioned in other posts here, darcs-2 versus darcs-1 was sort of built this way too). Sometimes it can be easier to prototype and/or try entirely different directions without a backwards compatibility liability, and then come back to the "parent" project with working code and figure out the migration strategy then. One thing I see here (as a long time reader/follower of the space) is that pijul has been using other languages than Haskell and there's some thought that a more approachable language might bring in more developers outside of the subset of Haskell developers that have been darcs' main source of development experience.
- lvh 10y agoThe challenges with darcs' performance lie at the core of its theory of patches; IIUC, there's no way to make exponential merge go away without also breaking darcs. pijul changes the theory, and does so in a way specifically to avoid slow algorithms.
- maxpert 10y agoIs anyone using Darcs or Pijul at work?
- stestagg 10y agoI used darcs for a while a few years back, it was ok. But definitely less polished than git. Also the only vcs I've ever used where the repo managed to corrupt itself to the point I lost committed but unpushed changes
- angvp 10y agooh what a great idea, let's build pijulhub!
- X86BSD 10y agoHow is this different from, my personal favorite, Fossil. http://fossil-scm.org/index.html/doc/trunk/www/index.wiki http://fossil-scm.org/index.html/doc/trunk/www/index.wiki
- j_s 10y agoDo you have a moment to explain what makes Fossil your favorite? As far as I know, the only unique aspect of Fossil is "Integrated Bug Tracking, Wiki, and Technotes".
- X86BSD 10y agoThose are certainly very nice features to have. For me the syntax and ease of use is what I like. Although that is all subjective to each person of course. Plus the author is a great guy. No ego at all. Plus the license is more appealing to me.
- donpdonp 10y agoIs there any new status on this project? The last blog post from 2017-Jan-10 says "I’m pleased to announce that we are starting to test the first usable version of Pijul.We are not quite ready to release.." I was hoping that getting to the front page meant pijul had done a release but I see nothing to that effect.
- dgellow 10y agoI've shared the link because that's an interesting project and I'm interested in what people have to say. I wasn't expecting to reach the front page to be honest.
- ocharles 10y agohttps://twitter.com/acid2/status/811691084623527940 https://twitter.com/acid2/status/811691084623527940 has some update
- kabes 10y agoDo I understand it correctly if I say this is like the event-sourcing model applied to version control?
- gue5t 10y agoYes; "event sourcing" is a niche term for "maintaining a change log" which is quite literally the idea: keep patches, not states.
- tmsldd 10y ago$ alias pjl 'pijul' ... much better now..
- alkonaut 10y agoSays it's only text yet - is there a plan for binary? Does darcs work well with binary?
- WorldMaker 10y agoDarcs handles binaries, but not particularly well (ie, nothing quite next to the ease and brilliance of working with text documents). Binary merging is not well defined in general by any means, so binary is handled essentially at the entire file level. Because darcs patches need to [1] store the previous file state as well as the new/current one, patches in darcs with binary changes can get huge quickly. Optimizations have been added to darcs over the years including some changes to something increasingly akin to git's hash storage for binary objects, but so far as I know, binary files that might change a lot over time are still mostly discouraged in darcs. [1] To keep the patches reversible, for commutation.