I think the mantra of "Make simple things easy and hard things possible" applies here. These tools all do a poor job of the former. Now, if you're writing a lo

I think the mantra of "Make simple things easy and hard things possible" applies here. These tools all do a poor job of the former. Now, if you're writing a low-level tool (in git's terminology, plumbing), that doesn't matter as much, because it's designed to be wrapped; maintainability and (interface) stability probably take priority over being maximally intuitive. But if you're writing a tool for end users (including developers), some focus on UX is warranted. (How much each of these tools are intended for end users, can be argued separately, not by me)