I've started doing this with hashes in a CLI I'm working on. For slow prints, it's somewhat helpful https://asciinema.org/a/aD38Pk88CZgSZqtq but for debug dumps with many many hashes it really helps readability and tracking hashes across lines.

> it’s much easier to pick out the unique byte when it’s a different color! human brains are really good at spotting visual patterns—given the right format

Don't really see the advantage. Unique bytes have no unique meaning across data types.

The only good syntax highlight to me is 00 and perhaps FF. But that's my opinion of course.

Anything else that has no direct relation to what you're looking at is meaningless.

It'd be nicer if the hex coloring actually matched the "ascii" coloring as well. Orange on the left but green on the right does not help find things.

[dead]

[dead]

I actually stopped reading after the intro because I fundamentally disagreed with its premise. The "find the C0" took me about 1/4 second with uncoloured. Looking at the coloured took my eyes about 3 seconds to recover from the colour overload, then I was scanning down and found the colours so distracting with the constant switching between orange, pink and yellows than it took me a total of about 5 seconds to scan down as far as the blue C0. Maybe if it was all uncoloured and blue just for that, I might have actually noticed it looking different earlier.

It's been a while since I used hexedit on Linux, but I think that highlighted search results in reverse colours, just like less does for text search. Personally, I'd prefer that to colours.