@AlanMunn It's primarily more convenient, as it renames the file in the work space, while simultaneously removing the old name and adding the new one to the index. But the move is never recorded by git as a rename; it's just that a file has ceased to exist and a new file with the exact same contents has been added.
@AlanMunn In a sense, no old content can be screwed up in git, since files (and other objects) are stored in the repository index by the hash of their contents. But if you wish to move and edit a file, I would recommend moving it using git mv, committing it, and then editing. That should help commands like git blame to work better in the future.
@AlanMunn As is well known on this chat, blaming is important.
@tjt263 Well Overleaf has made LaTeX much more accessible since you don't have to install anything to use it. I'm fairly certain this has expanded the number of users significantly.
@AlanMunn ShareLaTeX has greatly simplified the work for the trainer who taught me the basics of LaTeX 4 years ago. Indeed, he did not need to install himself a LaTeX distribution on each of the computers in the classroom that was loaned to him by the academy (and moreover, he had neither the legal right nor the administrative privileges necessary to do so).
He simply had us create a ShareLaTeX account and join the group dedicated to this internship that he had specially created for the occasion.
@AlanMunn I believe that Git doesn't actual do file level tracking. A design decision, apparently. But the net has more about that than you could wish to know.