22 ms·
> There have been lots of projects over the last 10+ years that have been riffs on "It's Git, but <better in this way>", but none of them have really caught on
by IshKebab 3y ago
> There have been lots of projects over the last 10+ years that have been riffs on "It's Git, but <better in this way>", but none of them have really caught on beyond a small, admittedly passionate group.
I don't think so. The only ones I know of are Pijul and Jujitsu which you mentioned. They're both quite new.
> you're already doing centralized version control; you're just doing it with a confusing distributed version control UX
Sort of... But actually, as soon as you go offline it's distributed.
Anyway I think more alternatives is always better and lots of the issues you listed in the readme definitely need solving, so good luck!
- pmeunier 3y ago> The only ones I know of are Pijul and Jujitsu which you mentioned. They're both quite new. There are other Git frontends like Jujutsu: Gitless, StackedGit, GitButler, Sapling… Even the idea of "SVN is the next Git" (which is the thing here) isn't quite new, PlasticSCM did it already. Nothing like Pijul though, defining the actual problem carefully and rigorously, then actually solving it. > Sort of... But actually, as soon as you go offline it's distributed. Even online is distributed: Google Docs needs stuff from distributed computing such as OTs and CRDTs.