> versus saving binary project files where diffs/merges make little sense and can corrupt the output Diffs and merges with binary files can work just fine. Lo

> versus saving binary project files where diffs/merges make little sense and can corrupt the output Diffs and merges with binary files can work just fine. Look at rsync as an example. The problem is that it can take... too... much... time. Text is easy to diff because we can simplify the problem down to lines separated by `[\r]\n`. Being able to split a large text file into individual lines to delta is a much easier problem. Binary data is much more difficult. So the problem isn't corrupting an output file, but just how much time it can take to figure out the most efficient way to delta a file. Because of this time limit, it makes the workflow of revision control too unwieldy.