Pijul

Raised as a usability problem by 12 people on Hacker News over 9 years (2018–2026), in 8 threads.

People raised many different problems with Pijul, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 12 complaints

Repository state got corrupted right away during the intended workflow, with no warnings2026-04-11
No context lines on diffs, and no link to full-file diff from changeset2024-02-21
Lacks a git status-like command, so users can't easily see working copy state2024-02-21
Unclear how users resolve conflicts and interact with the patch graph2023-08-12
Couldn't figure out how to make a commit and push2023-08-12
Wildcard add fails with unhelpful error; identity setup is confusing and undocumented2022-01-19
Pijul is too slow to be usable in practice2021-04-08
Website install instructions didn't work with Nix; user had to guess options by googling2020-12-21
Couldn't find how to switch branches or revert patches; documentation links are 4042020-11-10
Page is very slow, then shows Not found; unclear where to register or sign in2020-11-09
Slow site, 'Not found' page, and no clear way to find source code2020-11-09
Documentation lacks a clear explanation of the patch theory2018-12-11