3 ms·
Blog hasn't been updated since April 2019 and, I don't know if the repo is supposed to be browser accessible, but https://nest.pijul.com/pijul_org/pijul https:/
by c17r 6y ago
Blog hasn't been updated since April 2019 and, I don't know if the repo is supposed to be browser accessible, but https://nest.pijul.com/pijul_org/pijul https://nest.pijul.com/pijul_org/pijul gives no useful response.
Looks interesting but don't know if I'd want to rely on it.
ETA: looks like their twitter account (https://twitter.com/pijul_org https://twitter.com/pijul_org) is still active to that's a good thing
- lapinot 6y agoafaik pmeunier is currently completely rewriting pijul (since ~1 year) privately so that he can focus on getting the important things right (core algorithms, repo representation) and not on fixing stuff. It's debatable but has been explained. Apparently we could see that 1.0 release soonish. Relevant thread: https://discourse.pijul.org/t/is-this-project-still-active-yes-it-is/451/25 https://discourse.pijul.org/t/is-this-project-still-active-y...
- c17r 6y agoThanks, that thread was a good read-thru. I can understand why it was done the way it was done but it makes it difficult for outsiders to know what's up. An occasional "State of Pijul" blog post would be helpful. As we all know, the Internet is full of somewhat finished but now stagnant projects.
- X6S1x6Okd1st 6y agoLast relevant comment by the Author: By the way, the main things that remain to be done before release are: make Git import incremental, at the moment it’s a one-off thing that doesn’t properly save its intermediate states. rebalance a few things between Pijul and Libpijul. Florent is taking care of this one. update the Nest for the new formats and new protocol. write documentation. In other words, we’re really close to a release.