Notices where this attachment appears
-
@efi @theoutrider You can use Mercurial as a human-friendly git front-end, I hear. Or maybe try http://gitless.com/ ?
-
@are0h @webinista I'm in favor of worse is better. If we didn't have the people come into git that we did, if Linus didn't get fed up with the loss of BitKeeper and hash out git over the weekend and then just roll with it, we wouldn't have git. Maybe we would have had Mercurial, which many people say is much less arcane and has an actual designed user experience in comparison -- but then again maybe Mercurial wouldn't have been in the state it is without the competition of git.
So maybe people generally use git the https://xkcd.com/1597/ way and maybe that works. And maybe if people mess their repo up they can just nuke it and clone a new one instead of spending the weekend finding out what happened and how git actually really works.
But I'm hoping that something like http://gitless.com/ can replace #xkcd1597 and still let us keep the history of git repos that we have now, and if it's *really* necessary to do some serious git surgery maybe someone who already wasted time on learning the idiosyncracies, like you or me, can take care of that with good old/bad git.
You can do some really neat stuff with git, but the problem is you *have* to do some really neat stuff to get by in everyday situations.
-
@moonman Have you looked at http://gitless.com ?
-
Two well-written and interesting articles that both touch on path dependence in the evolution of software:
http://adamierymenko.com/privileged-ports-are-causing-climate-change/
https://redfin.engineering/two-commits-that-wrecked-the-user-experience-of-git-f0075b77eab1
Good discussions going on where @dthompson shared them:
https://toot.cat/users/dthompson/updates/36745
https://toot.cat/users/dthompson/updates/36819
The redfin post ends up recommending https://people.gnome.org/~newren/eg/ , which reminds me I still haven't had a look at http://gitless.com/ , which is the same but different.
Speaking of git, wouldn't it have been great if I could have just made this a Merge Reply to both of Dave's posts? Now I just made an independent post, because I don't think it belongs more to either discussion.
Of course the UI considerations of Merge Reply are daunting. Or maybe they aren't: #pleroma is doing a pretty good job of handling complex reply trees by flattening yet providing context links and popups. In that kind of interface, just adding another parent link isn't a biggie.