4 ms·
Because of the way most non-text files are encoded, it's nearly impossible to collate changes in the way a VCS requires. At work we're using a graphics engine w
by jschwartzi 12y ago
Because of the way most non-text files are encoded, it's nearly impossible to collate changes in the way a VCS requires. At work we're using a graphics engine which stores layout data in binary blobs, then exports those to XML(Don't ask me why, I don't know). As a result, you would have to use their IDE tool to perform any merges, and because of that you can't annotate/blame the file at all, which eliminates a lot of the usefulness of the VCS as a repository of history.
When companies start shipping real comparison tools for their binaries then you might see more widespread adoption.
- davidgerard 12y agoI don't mean just that - I mean, you can save flat uncompressed ODTs into git and get most of what programmers get from it. Solving the blobs issue won't solve the fear issue.