I've personally settled on running diff's output into diff-highlight (supplied with Git!) and into ansi2html (one of them; there are many versions of it, and you can write one yourself in about 20 minutes, you only really need very few escape sequences handled, and then wrangle with CSS for additional 2 hours), and calling xdg-open on the temporary file. A neat pipeline, all in all.
The point about textconv being sufficient in many cases is worth emphasizing — the cases where you actually need a full diff driver are when the file has semantics that text diff destroys. OpenAPI specs are a good example: a field rename looks like a deletion + addition in text diff but is a single semantic change.
I ran into the same thing building a semantic diff for a DSL compiler — text diff would report noise on every whitespace or reorder change, but the meaningful question is "which fields changed type, which statements were added or removed." Once you're operating on the AST the signal-to-noise ratio is completely different.
I bet there might be something but you can probably create your own by using ImageMagick[1] and some manipulations. For ex. for images, I would create a temp file or use a process substitition + open on OSX or xdg-open on Linux. Here is a first post about
Or you can make it even easier(cause the output is only a text) and simply print out the difference in metadata directly. You might need some other tools like ImageMagick but at least no shenanigans with viewing binary data as part of your diff.
https://diff2html.xyz/
reply