That "git blame" is called that instead of "git credit" or the like is an example of needed emotional labor not being performed in tech.
One doesn't "blame" their teammates for the code that works, which usually constitutes the bulk of a code base.
@jaycie I like that Debian actually lets you file kudos against packages as well as bugs.
@jaycie What about git praise?
@jaycie it's also something created by Linus Torvalds and he's pretty representative of how people act in the field
@clar Yep. You can bet I thought about exactly that as I wrote that toot.
True. I only ever use "git blame" when I wonder, "Who the f*** wrote this?"
I never use it when I see good code. I just assume I know which teammate did it. Not saying that is ideal, but it is what it is...
@jaycie I like that mercurial has "praise" and "blame" aliases for the connotation-free base command, "annotate"
@jaycie glorious point! 🌞🌞🌞
@jaycie I always understood it as a pretty light-hearted cultural joke.
@isagalaev Might well have been the intention. Unfortunately, jokes often translate poorly over text and even more so for users years-removed from the context. :/
@jaycie I believe one of the oldest such commands was called "annotate" in CVS.
The "svn blame" command was first added in 2003 (https://svn.apache.org/r847463) and just few days later it was aliased to "praise" (https://svn.apache.org/r847750)
It seems other version control systems copied the name "blame" but not its more positive alias 😕
@jaycie Sorry,, of course I put a typo in one of the links: https://svn.apache.org/r847650
@jaycie "we don't care about your work until you break shit. then we wanna know its your fault. that's all we'll use this for"