Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"There are only two hard things in Computer Science: cache invalidation and naming things." - Phil Karlton [0]

Based on the above statement, I find it extremely weird to see such git command named "blame", then I realized I'm not the only one:

What does 'git blame' do? [1].

Blame someone else for your bad code [2].

Git blame should be called git credit [3].

Does Git Blame sound too negative? [4].

______________________________

0. https://skeptics.stackexchange.com/questions/19836/has-phil-...

1. https://stackoverflow.com/questions/31203001/what-does-git-b...

2. https://news.ycombinator.com/item?id=27963868

3. https://dev.to/damcosset/git-blame-should-be-called-git-cred...

4. https://www.reddit.com/r/ProgrammerHumor/comments/r5lzyo/doe...



I think `blame` is on-brand for a tool called `git`.


agreed, i renamed [1] it to ‘who’ (well, actually it’s just ‘w’ since i’m a vim-diehard)

[1] https://github.com/looshch/configs/blob/master/.gitconfig#L1...


I think a better name would be “git praise”


I'm sure you know this, but for younger readers, in Subversion 'praise' was an alias for 'blame'.

For neutrality, 'annotate’ was another alias.


One advantage that "git blame" has over possible alternatives such as "git credit", "git author", or "git praise", is that it's one character shorter and maybe faster to type.

For the same number of characters, I have heard of "git glory" as a possible alternative.


and off-by-one errors.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: