Presumably the impetus is that if you fix a bunch of small things in a single commit it might be easier to compile the list of small things you changed by noting them as comments as you fix them rather than trying to remember them after the fact when it comes time to write a commit log for that commit.

That said, philosophically I'd personally prefer to just commit the small features individually as a set of small commits, therefore you get a better git blame/praise experience with the end result, but I realize there is a wide spectrum of preferences on commit size and style.

It's not the same thing at all.

Git blame displays the last commits that updated your files lines.

This gives you the ability to write your commit description while you code.

git blame shows you commit messages for already-committed code.

This builds the initial commit message when you want to commit the pending changes in the index.