Comments by "Mikko Rantalainen" (@MikkoRantalainen) on "A New Git Diff Algo" video.

Is somebody still using some diff tools that do not support "ignore white space change"? Even gitk has an UI toggle for that and on command line GNU diff supports -Z, -b, -W, -B, -I to support different kinds of whitespace ignore that you might want to have.
1
26:00 I have to agree that the suggested metric doesn't make sense. Basic diff has just two operators: remove line or add a line. When you read diff, red lines have been removed, green lines have been added. Really simple. This new improved format may reduce number of lines slightly but in return you get a LOT more complex operators. Instead of thinking "is this line red or green?" I have to think "is this line deleted, added, moved, copied or just white-space adjusted?" – for every single line of code repeatedly. I think having a normal diff reader that supports "Identical segments with more than 5 lines are collapsed by default and rendered with summary "Moved function XYZ". That is, an improved tool for reading the existing diffs would be much superior method. I think the whole stuff was designed by a non-programmer who totally failed to understand what actually matters. If I were interested in lines of text, I wouldn't use 15 line context for my diffs.
1