I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.
-
I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.
Which is a problem, because Git came out in 2005
-
I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.
Which is a problem, because Git came out in 2005
-
@Kaution obviously i already use a gui for git
-
I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.
Which is a problem, because Git came out in 2005
@andrewt i use hg-git, life is good.
-
I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.
Which is a problem, because Git came out in 2005
@andrewt The mansplaining replies you’re getting also date back to the 1970s 🫠
-
I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.
Which is a problem, because Git came out in 2005
@andrewt @bitprophet TBF, git managed to accumulate the same volume of cruft in less than half the time.
-
I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.
Which is a problem, because Git came out in 2005
@andrewt I vividly remember not having used it through university in the 2000s and *still* get the impression it was written in the 70s. Git was perfect for Linus, and I think y combinator hacker culture and personality cults are the reason we now have to have a distributed vcs in that style for everything…
-
@andrewt i use hg-git, life is good.
@lritter I guess my worry with hg-git is that it'd be like using a Dvorak keyboard — sure, it's easier while I'm doing it, but I still need to know how to type on Qwerty but now I'm context switching
-
@lritter I guess my worry with hg-git is that it'd be like using a Dvorak keyboard — sure, it's easier while I'm doing it, but I still need to know how to type on Qwerty but now I'm context switching
@andrewt it's not just a frontend - the local repo is in mercurial format. i used mercurial for the past 15 years; but since service for hg is growing scarce and undersupported, i now also use it transparently with an online git repo.
been doing so since a few years. never had to fiddle with git directly once.
only snag to take care of is to maintain a bookmark.current in the .hg folder so hg auto-updates the master/whatever-it-is-now-called tag.
-
@andrewt it's not just a frontend - the local repo is in mercurial format. i used mercurial for the past 15 years; but since service for hg is growing scarce and undersupported, i now also use it transparently with an online git repo.
been doing so since a few years. never had to fiddle with git directly once.
only snag to take care of is to maintain a bookmark.current in the .hg folder so hg auto-updates the master/whatever-it-is-now-called tag.
@lritter I mean that sounds fine and all, but I last used Mercurial in 2012 and as you say, git documentation is markedly easier to come by these days (even if that is partly because you rely on it more)
Are there decent GUIs out there that support hg?
-
@lritter I mean that sounds fine and all, but I last used Mercurial in 2012 and as you say, git documentation is markedly easier to come by these days (even if that is partly because you rely on it more)
Are there decent GUIs out there that support hg?
@andrewt i never need any mercurial documentation because its command line interface is not insane.
there are no decent GUIs for mercurial, which is why git won out in the first place - the aforementioned bonkers command-line caused a proliferation of GUIs.
i used to use GUIs about 20 years ago but found that i work so much in terminals that it makes no sense to even reach for the mouse.
-
@andrewt i never need any mercurial documentation because its command line interface is not insane.
there are no decent GUIs for mercurial, which is why git won out in the first place - the aforementioned bonkers command-line caused a proliferation of GUIs.
i used to use GUIs about 20 years ago but found that i work so much in terminals that it makes no sense to even reach for the mouse.
@lritter Yeah, sounds like we have kinda different use cases — I tend not to touch the terminal unless I need to. A CLI VC system is ok if I'm writing like a Node or Python app where I'm in and out of the terminal all day, but if I'm noodling about in Godot or something, I'm firmly in GUI-land
-
I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.
Which is a problem, because Git came out in 2005
@andrewt I've always been extremely confused how people were using Git on the command line, because it's just so arcane. My GUI pick was Git Graph in VSCode.
But once I picked up jujutsu last year even doing rebases on the command line suddenly became incredibly easy. JJ proves that the Git frontend is really badly designed, since it takes the same backend (full compatibility) and builds a much more orthogonal set of operations on top.
https://steveklabnik.github.io/jujutsu-tutorial/introduction/what-is-jj-and-why-should-i-care.html -
I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.
Which is a problem, because Git came out in 2005
@andrewt one problem with git is that its designers and early users had only just barely escaped the vile clutches of other, worse version control systems and all of the early users only wanted the smallest possible filesystem mutation primitives in order to automate their workflows.
The git command line interface works great in CI/CD and scripting to make efficient sequences of operations. If that's not the way you use the tool, then uh yes very much the set of operations is hard to use and remember. Otherwise you have to internally copy the understanding of the first two power users in order to use it well.
I wish there was a discussion of "the trauma of using X made me design Y to be like this and that" and how it might be difficult to use Y if you didn't have those experiences with X.
-
I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.
Which is a problem, because Git came out in 2005
@andrewt rofl
-
R relay@relay.infosec.exchange shared this topic
