CUE documentation should talk about whether terser diffs are selling point

[paul-hammant]

You know, like what git-diff would say about an item added to a list - how many lines does the underlying diff engine think has changed

[xinau]

Thanks for your suggestion. I think it would be a good idea to add this feature to the documentation once #8 is implemented :)

[paul-hammant]

I don't think so. This is a function of Git, Mercurial, Svn, Perforce, PlasticSCM. How pretty are diffs in that tech (unified diff really), for a number of change scenarios. And I say that becuase the at-rest format for CUE things is carriage-return delimited text (UTF8, or a codepage, etc), is it not??

[xinau]

@paul-hammant could you please elaborate a little bit more and provide an example on your issue/request as I'm struggling to understand the underlying issue.

[paul-hammant]

$> diff ABCv1.toml ABCv2.toml

What does that diff look like (but CUE source not .txt files)? Is it noisy for a given scenario, or terse? If XML is OK for diffs (for that scenario). JSON is noisy because of the commas. What does CUE diffs look like?