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— 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 to Git, and I did it by experimenting and I eventually proving a viable path using Git's built-in, two-way SVN bridge, which is excellent.
Whenever I revisit Pijul, I play with importing a giant (pathological, tbh) Git repository. Unfortunately, it runs for days and has never successfully completed for me. But the moment that bridge is good enough, I'm in! (Performance is nice but reliability is obviously the essential thing, especially when it comes to one-time operations like the initial import.)
PS: pmeunier, if you're reading this: I love your work. When Pijul can reliably import Nixpkgs, write a killer blog post about it. I'm sure it'll blow up here on HN. :)
And thanks for your work to advance the state of the art in DVCS! :)
PPS: I wonder if Pijul's fundamentally better merging behavior could become especially salient for teams (or individuals) whose codebases are seeing a lot of churn with heavy LLM use, so that it can help make automatic resolution of merge queues cheaper or easier or more reliable.
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 to Git, and I did it by experimenting and I eventually proving a viable path using Git's built-in, two-way SVN bridge, which is excellent.
Whenever I revisit Pijul, I play with importing a giant (pathological, tbh) Git repository. Unfortunately, it runs for days and has never successfully completed for me. But the moment that bridge is good enough, I'm in! (Performance is nice but reliability is obviously the essential thing, especially when it comes to one-time operations like the initial import.)
PS: pmeunier, if you're reading this: I love your work. When Pijul can reliably import Nixpkgs, write a killer blog post about it. I'm sure it'll blow up here on HN. :)
And thanks for your work to advance the state of the art in DVCS! :)
PPS: I wonder if Pijul's fundamentally better merging behavior could become especially salient for teams (or individuals) whose codebases are seeing a lot of churn with heavy LLM use, so that it can help make automatic resolution of merge queues cheaper or easier or more reliable.