3 ms·
1. implement the patch category that Pijul uses 2. compose the patches 3. either you have a nice diff to show the user, or an explanation of why that is not p
by aeneasmackenzie 6y ago
1. implement the patch category that Pijul uses
2. compose the patches
3. either you have a nice diff to show the user, or an explanation of why that is not possible, like "Can't show you the composition of A, X, Q because X depends on C"
Unfortunately they keep rewriting pijul from scratch.
- fififi 6y agoThe misfortune isn't that Dev's aren't doing anything. The misfortune is that loud mouthed people on places like this are opinionated and dumb. I just read a comment where the poster said json should be mandated by law because a free service didn't provide json. And he is definitely not fringe, this is 90% of the css philosophers here. He has 37 000 points. Ye ls 37 thousand.
- dilap 6y agoI am excited about the current rewrite though since (if it lives up to the hype) it'll bring performance good enough to use Pijul for non-tiny projects. Not sure if Pijul will be the software to do it, but someday we'll all be using patch-based VCSs and look back at graph-based models like git the same way we look at non-DVCS today.