{"slug": "pijul", "name": "Pijul", "category": "git", "category_name": "Git and code hosting", "description": "", "recommenders": 6, "commenters": 13, "warners": 1, "score": 5.795, "rising": -1.96, "first": "2026-01-27", "latest": "2026-09-13", "why": "Pijul seems great and I really want it to flourish.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 6, "neutral": 4, "compare": 2, "warn": 2}, "spark": [0, 0, 1, 0, 2, 2, 0, 1, 0, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "Pijul seems great and I really want it to flourish.", "kind": "", "icon": false, "domain": "pijul.org", "github_repo": null, "official_url": "https://pijul.org", "pricing": "", "aliases": ["Pijul"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 777148705, "item_id": 48571794, "url": "https://news.ycombinator.com/item?id=48571794", "by": "VorpalWay", "date": "2026-06-17", "version": null, "stance": "recommend", "quote": "There are some projects:", "excerpt": "There are some projects: * https://github.com/jj-vcs/jj * https://nest.pijul.com/pijul/pijul", "context": "", "use_case": "", "switched_from": "", "story": "Epic Games announces Lore version control system"}, {"id": 763864560, "item_id": 47741535, "url": "https://news.ycombinator.com/item?id=47741535", "by": "pxc", "date": "2026-04-12", "version": null, "stance": "recommend", "quote": "Pijul seems great and I really want it to flourish.", "excerpt": "Pijul seems great and I really want it to flourish. I love reading the blog posts when there are major updates, and its approach seems fundamentally more right than Git's (as it should\u2014 while it gets its core theory elsewhere, its UX learns from Git pain). What I'm waiting for before I switch is mainly a really good bridge to Git. At the first couple tech companies I worked at, I led efforts to switch from Subversion", "context": "led Subversion to Git migrations at tech companies", "use_case": "version control", "switched_from": "", "story": "Pijul a FOSS distributed version control system"}, {"id": 763624339, "item_id": 47726521, "url": "https://news.ycombinator.com/item?id=47726521", "by": "johnisgood", "date": "2026-04-10", "version": null, "stance": "recommend", "quote": "I am rooting for pijul", "excerpt": "I like darcs, so I am rooting for pijul. https://pijul.com", "context": "", "use_case": "", "switched_from": "", "story": "We've raised $17M to build what comes after Git"}, {"id": 759765024, "item_id": 47485314, "url": "https://news.ycombinator.com/item?id=47485314", "by": "toomim", "date": "2026-03-22", "version": null, "stance": "recommend", "quote": "It's a dramatic model shift -- and is awesome.", "excerpt": "Pijul does both. It's a VCS, that is a CRDT, that preserves conflicts until a human resolves them. Look it up: https://pijul.org It also makes cherrypicking and rebasing wayyyy easier. You can actually add or remove any set of patches, at any time, on any peer. It's a dramatic model shift -- and is awesome.", "context": "", "use_case": "", "switched_from": "", "story": "A Coherent Vision for the Future of Version Control"}, {"id": 759671984, "item_id": 47479499, "url": "https://news.ycombinator.com/item?id=47479499", "by": "simonw", "date": "2026-03-22", "version": null, "stance": "recommend", "quote": "because Pijul uses Pijul for development, not Git and GitHub!", "excerpt": "I hadn't heard of Pijul. My first search took me tohttps://github.com/8l/pijul which hasn't been updated in 11 years, but it turns out that's misleading and the official repo at https://nest.pijul.com/pijul/pijul had a commit last month. ... and of course it is, because Pijul uses Pijul for development, not Git and GitHub!", "context": "", "use_case": "", "switched_from": "", "story": "A Coherent Vision for the Future of Version Control"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 763773184, "item_id": 47735824, "url": "https://news.ycombinator.com/item?id=47735824", "by": "WhyNotHugo", "date": "2026-04-11", "version": null, "stance": "warn", "quote": "diffs can't show context", "excerpt": "I like the idea of Pijul, and checked it out a couple of years ago. Some basic quality of life features were missing, and are still missing. For example, diffs can't show context. They show lines removed and added, but can't show the previous and following line because of implementation details. Here's a diff: https://nest.pijul.com/pijul/pijul/changes/OMGL7JBCLSHWTIYP7LSQXSUGBTIQFBD7VVCZCD27AORPOKOBTVMAC It's a litt", "context": "", "use_case": "", "switched_from": "", "story": "Pijul a FOSS distributed version control system"}, {"id": 759790272, "item_id": 47486892, "url": "https://news.ycombinator.com/item?id=47486892", "by": "QuiCasseRien", "date": "2026-03-23", "version": null, "stance": "warn", "quote": "still not production ready", "excerpt": "I will look at it, it seems interesting. However, i hope a better ending than Pyjul (https://pijul.org/). I'm no longer waiting for it whereas everything sound awesome : quite no more merge conflict and patches order free. So sad it's still not production ready.", "context": "", "use_case": "", "switched_from": "", "story": "A Coherent Vision for the Future of Version Control"}]}], "who": [{"by": "pxc", "context": "led Subversion to Git migrations at tech companies", "url": "https://news.ycombinator.com/item?id=47741535", "date": "2026-04-12"}], "tags": [], "use_cases": ["version control for agents", "version control", "version control experiment"], "compared": [{"slug": "git", "name": "Git", "co": 7, "switched_from": 1, "switched_to": 0}, {"slug": "darcs", "name": "Darcs", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "nix", "name": "Nix", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "jujutsu", "name": "Jujutsu", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [{"id": 801488080, "item_id": 50093005, "url": "https://news.ycombinator.com/item?id=50093005", "by": "pmeunier", "date": "2026-10-14", "version": null, "stance": "recommend", "quote": "As the author of Pijul, I've been using it to build giant things", "excerpt": "As the author of Pijul, I've been using it to build giant things using hundreds of Claude instances in parallel, almost without any conflict, ever. Some are already public, like my replacement of Nix (https://nest.pijul.com/elpe/elpe). Others aren't public yet, but are even much bigger in terms of scope and difficulty. It seems Anthropic didn't understand the difference between a distributed file system and version c", "context": "author of Pijul", "use_case": "", "switched_from": "", "story": "Redesigning source control at Anthropic"}], "threads": [{"url": "https://news.ycombinator.com/item?id=47478401", "title": "A Coherent Vision for the Future of Version Control", "mentions": 7}, {"url": "https://news.ycombinator.com/item?id=47672941", "title": "Pijul a FOSS distributed version control system", "mentions": 3}, {"url": "https://news.ycombinator.com/item?id=50073633", "title": "Redesigning source control at Anthropic", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49649864", "title": "From Git to Fossil (2025)", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48571081", "title": "Epic Games announces Lore version control system", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47712656", "title": "We've raised $17M to build what comes after Git", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {"recommend": 1}, "2026-02": {}, "2026-03": {"recommend": 2, "neutral": 3, "compare": 1, "warn": 1}, "2026-04": {"recommend": 2, "warn": 1, "compare": 1}, "2026-05": {}, "2026-06": {"recommend": 1}, "2026-07": {}, "2026-08": {}, "2026-09": {"neutral": 1}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 801630080, "item_id": 50101880, "url": "https://news.ycombinator.com/item?id=50101880", "by": "pmeunier", "date": "2026-10-15", "version": null, "stance": "recommend", "quote": "", "excerpt": "Yes! I've been using it with a massive farm of agents to build large things, such as a replacement for Nix (https://nest.pijul.com/elpe/elpe), and other large things.", "context": "", "use_case": "Version control for agents", "switched_from": "", "story": "Redesigning source control at Anthropic"}, {"id": 794946208, "item_id": 49684138, "url": "https://news.ycombinator.com/item?id=49684138", "by": "QuiCasseRien", "date": "2026-09-13", "version": null, "stance": "neutral", "quote": "Did you try pijul", "excerpt": "Did you try pijul (https://pijul.org/) ?", "context": "", "use_case": "", "switched_from": "", "story": "From Git to Fossil (2025)"}, {"id": 777148705, "item_id": 48571794, "url": "https://news.ycombinator.com/item?id=48571794", "by": "VorpalWay", "date": "2026-06-17", "version": null, "stance": "recommend", "quote": "There are some projects:", "excerpt": "There are some projects: * https://github.com/jj-vcs/jj * https://nest.pijul.com/pijul/pijul", "context": "", "use_case": "", "switched_from": "", "story": "Epic Games announces Lore version control system"}, {"id": 763864560, "item_id": 47741535, "url": "https://news.ycombinator.com/item?id=47741535", "by": "pxc", "date": "2026-04-12", "version": null, "stance": "recommend", "quote": "Pijul seems great and I really want it to flourish.", "excerpt": "Pijul seems great and I really want it to flourish. I love reading the blog posts when there are major updates, and its approach seems fundamentally more right than Git's (as it should\u2014 while it gets its core theory elsewhere, its UX learns from Git pain). What I'm waiting for before I switch is mainly a really good bridge to Git. At the first couple tech companies I worked at, I led efforts to switch from Subversion", "context": "led Subversion to Git migrations at tech companies", "use_case": "version control", "switched_from": "", "story": "Pijul a FOSS distributed version control system"}, {"id": 763777472, "item_id": 47736092, "url": "https://news.ycombinator.com/item?id=47736092", "by": "WolfeReader", "date": "2026-04-11", "version": null, "stance": "compare", "quote": "Pijul fixed this, at least!", "excerpt": "Speaking as a former Darcs user (Darcs is another patch-based VCS that Pijul draws inspiration from): \"This is a useless property because the graph is only encoded at the patch layer. In the real world you have far more semantic dependencies than patch dependencies. ie, I have a patch that adds a function that calls a function added in another patch. Pijul doesn't know about that.\" Darcs solved this in two different ", "context": "", "use_case": "", "switched_from": "", "story": "Pijul a FOSS distributed version control system"}, {"id": 763773184, "item_id": 47735824, "url": "https://news.ycombinator.com/item?id=47735824", "by": "WhyNotHugo", "date": "2026-04-11", "version": null, "stance": "warn", "quote": "diffs can't show context", "excerpt": "I like the idea of Pijul, and checked it out a couple of years ago. Some basic quality of life features were missing, and are still missing. For example, diffs can't show context. They show lines removed and added, but can't show the previous and following line because of implementation details. Here's a diff: https://nest.pijul.com/pijul/pijul/changes/OMGL7JBCLSHWTIYP7LSQXSUGBTIQFBD7VVCZCD27AORPOKOBTVMAC It's a litt", "context": "", "use_case": "", "switched_from": "", "story": "Pijul a FOSS distributed version control system"}, {"id": 763624339, "item_id": 47726521, "url": "https://news.ycombinator.com/item?id=47726521", "by": "johnisgood", "date": "2026-04-10", "version": null, "stance": "recommend", "quote": "I am rooting for pijul", "excerpt": "I like darcs, so I am rooting for pijul. https://pijul.com", "context": "", "use_case": "", "switched_from": "", "story": "We've raised $17M to build what comes after Git"}, {"id": 759790272, "item_id": 47486892, "url": "https://news.ycombinator.com/item?id=47486892", "by": "QuiCasseRien", "date": "2026-03-23", "version": null, "stance": "warn", "quote": "still not production ready", "excerpt": "I will look at it, it seems interesting. However, i hope a better ending than Pyjul (https://pijul.org/). I'm no longer waiting for it whereas everything sound awesome : quite no more merge conflict and patches order free. So sad it's still not production ready.", "context": "", "use_case": "", "switched_from": "", "story": "A Coherent Vision for the Future of Version Control"}, {"id": 759765024, "item_id": 47485314, "url": "https://news.ycombinator.com/item?id=47485314", "by": "toomim", "date": "2026-03-22", "version": null, "stance": "recommend", "quote": "It's a dramatic model shift -- and is awesome.", "excerpt": "Pijul does both. It's a VCS, that is a CRDT, that preserves conflicts until a human resolves them. Look it up: https://pijul.org It also makes cherrypicking and rebasing wayyyy easier. You can actually add or remove any set of patches, at any time, on any peer. It's a dramatic model shift -- and is awesome.", "context": "", "use_case": "", "switched_from": "", "story": "A Coherent Vision for the Future of Version Control"}, {"id": 759730912, "item_id": 47483182, "url": "https://news.ycombinator.com/item?id=47483182", "by": "ozten", "date": "2026-03-22", "version": null, "stance": "neutral", "quote": "pijul clone https://nest.pijul.org/pijul/pijul", "excerpt": "pijul clone https://nest.pijul.org/pijul/pijul pijul log --hash-only > all_changes.txt pijul unrecord --all git init ``` for HASH in $(cat all_changes.txt); do pijul apply \"$HASH\" pijul reset # sync working copy to channel state git add -A git commit -m \"pijul change: $HASH\" done ``` git remote add origin git@github.com:you/pijul-mirror.git git push -u origin main", "context": "", "use_case": "", "switched_from": "", "story": "A Coherent Vision for the Future of Version Control"}, {"id": 759696976, "item_id": 47481061, "url": "https://news.ycombinator.com/item?id=47481061", "by": "hackrmn", "date": "2026-03-22", "version": null, "stance": "compare", "quote": "where changes are patches and are commutative", "excerpt": "When you say \"unit of work\", unit of _which_ work are you referring to? The problem with rebasing is that it takes one set of snapshots and replays them on top of another set, so you end up with two \"equivalent\" units of work. In fact they're _the same_ indeed -- the tree objects are shared, except that if by \"work\" you mean changes, Git is going to tell you two different histories, obviously. This is in contrast wit", "context": "", "use_case": "", "switched_from": "", "story": "A Coherent Vision for the Future of Version Control"}, {"id": 759684816, "item_id": 47480301, "url": "https://news.ycombinator.com/item?id=47480301", "by": "vova_hn2", "date": "2026-03-22", "version": null, "stance": "neutral", "quote": "Currently, I'm about 6 years into the experiment.", "excerpt": "I have a weird hobby: about once a year I go to the theory page [0] in pijul manual and see if they have fixed the TeX formatting yet. You would think that if a better, more sound model of storing patches is your whole selling point, you would want to make as easy as possible for people who are interested in the project to actually understand it. It is really weird not to care about the first impression that your man", "context": "", "use_case": "Version control experiment", "switched_from": "", "story": "A Coherent Vision for the Future of Version Control"}, {"id": 759673536, "item_id": 47479596, "url": "https://news.ycombinator.com/item?id=47479596", "by": "idoubtit", "date": "2026-03-22", "version": null, "stance": "neutral", "quote": "", "excerpt": "The canonical website is https://pijul.org. The homepage has a link to the pijul source repository.", "context": "", "use_case": "", "switched_from": "", "story": "A Coherent Vision for the Future of Version Control"}, {"id": 759671984, "item_id": 47479499, "url": "https://news.ycombinator.com/item?id=47479499", "by": "simonw", "date": "2026-03-22", "version": null, "stance": "recommend", "quote": "because Pijul uses Pijul for development, not Git and GitHub!", "excerpt": "I hadn't heard of Pijul. My first search took me tohttps://github.com/8l/pijul which hasn't been updated in 11 years, but it turns out that's misleading and the official repo at https://nest.pijul.com/pijul/pijul had a commit last month. ... and of course it is, because Pijul uses Pijul for development, not Git and GitHub!", "context": "", "use_case": "", "switched_from": "", "story": "A Coherent Vision for the Future of Version Control"}, {"id": 748483760, "item_id": 46780235, "url": "https://news.ycombinator.com/item?id=46780235", "by": "mkleczek", "date": "2026-01-27", "version": null, "stance": "recommend", "quote": "Much more principled (and hence less of a foot-gun) way of handling conflicts is making them first class objects in the repository, like https://pijul.org does.", "excerpt": "Much more principled (and hence less of a foot-gun) way of handling conflicts is making them first class objects in the repository, like https://pijul.org does.", "context": "", "use_case": "", "switched_from": "Git", "story": "I made my own Git"}]}