Eh, just dust off graph theory and read Git Book like 3 times and you'll be fine /s.
But DVCS is just a bit of complex system to get. "Good UI" in this case is just finding enough common use cases and making them easy that the average mortal won't have to think what commands they type actually do. Case in point:
> Edit: also I know invariably someone will say to make my own Ui instead of complaining. I’ve tried. I’ve done some novel things but it’s really hard to do from a top down level without also rethinking some of the base interaction model. That’s a battle I think needs a lot of effort across the stack first.
as did many other. DVCS is a distributed system(doh) and those generally make reasoning hard for ones not used to thinking that way.
Aside from that I think git would benefit greatly if it had --explain command that would try to explain in human terms what the command you're trying to run actually does
But DVCS is just a bit of complex system to get. "Good UI" in this case is just finding enough common use cases and making them easy that the average mortal won't have to think what commands they type actually do. Case in point:
> Edit: also I know invariably someone will say to make my own Ui instead of complaining. I’ve tried. I’ve done some novel things but it’s really hard to do from a top down level without also rethinking some of the base interaction model. That’s a battle I think needs a lot of effort across the stack first.
as did many other. DVCS is a distributed system(doh) and those generally make reasoning hard for ones not used to thinking that way.
Aside from that I think git would benefit greatly if it had --explain command that would try to explain in human terms what the command you're trying to run actually does