AppDNA VS Pijul

AppDNA

AppDNA is a small XCode shell script which efficiently packages a Mac OS X Application's source...

Pijul

Pijul is a free and open source distributed version control system based on a sound theory of...

Landing page //
2019-08-31

Landing page //
2021-10-01

Pijul

Website: pijul.org

Edit details

Category Popularity

0-100% (relative to AppDNA and Pijul)

Pijul

Project Management

100 100%

Project Management

0% 0

Code Collaboration

12 12%

Code Collaboration

88% 88

Git

8 8%

Git

92% 92

Git Tools

9 9%

Git Tools

91% 91

User comments

Share your experience with using AppDNA and Pijul. For example, how are they different and which one is better?

Social recommendations and mentions

Based on our record, Pijul seems to be more popular. It has been mentiond 42 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

AppDNA mentions (0)

We have not tracked any mentions of AppDNA yet. Tracking of AppDNA recommendations started around Mar 2021.

Pijul mentions (42)

Version Control Beyond Git
The feature I think I would most like to see is support for patches as a more first-class object. For example reverts and cherry picks have no real metadata. This leads to conflicts when merging branches that have cherry picks (although they often auto-resolve if they are exactly the same diff) and makes asking "Does $branch contain $patch" basically impossible to answer. https://pijul.org/ greatly improves this... - Source: Hacker News / 7 days ago
Pijul is a free and open source (GPL2) distributed version control system
In Pijul, conflicts are not modelled as a "failure to merge", but rather as the standard case. Specifically, conflicts happen between two changes, and are solved by one change. The resolution change solves the conflict between the same two changes, no matter if other changes have been made concurrently. Once solved, conflicts never come back. - from https://pijul.org/. - Source: Hacker News / 3 months ago
Josh: Just One Single History
Do not try and bend the spoon, that's impossible. Instead, only try to realize the truth...there is no spoon. Then you will see it is not the spoon that bends, it is only yourself -- what Pijul users say when they overhear git users arguing with each other about monorepos. https://pijul.org/. - Source: Hacker News / 3 months ago
Introduction to Loro's Rich Text CRDT
I believe that handling merges like this correctly was a motive for designing pijul: https://pijul.org See the item on the splash page about 'merge correctness'. Unfortunately I wasn't able to find the post detailing the behavior with a bit of searching. - Source: Hacker News / 4 months ago
Introduction to Loro's Rich Text CRDT
Darcs [0] patch theory was a predecessor to OTs/CRDTs (and a predecessor to git as well; in some ways it is the "smart" to which git was named "dumb"). When it works and performs well it is still sometimes version control magic. Pijul [1] is an interesting experiment to watch, trying to keep the patch theory flag flying and also trying to bring in updates from OTs and CRDTs as it can. [0] https://darcs.net [1]... - Source: Hacker News / 4 months ago