> I Love XML. Well-designed XML is better than well-designed JSON IMHO for human readability.

But both are absolutely inferior to S-expressions. Compare this (from https://www.xml.com/pub/a/2004/07/21/design.html):

    <books xmlns='http://www.example.com/books'>
    
      <book publisher="Addison Wesley">
    
        <title>Mythical Man Month</title>
    
        <author>Frederick Brooks</author>
    
        <publication-date>1995-06-30</publication-date>
    
      </book>
    
      <book publisher="Apress">
    
        <title>Programmer’s Introduction to C#</title>
    
        <author>Eric Gunnerson</author>
    
     <publication-date>2001-06-30</publication-date>
    
      </book>   
    
    </books>

to this:

    (books (ns "http://www.example.com/books")
           (book (publisher "Addison Wesley")
                 (title "Mythical Man Month")
                 (publication-date "1995-06-30"))
           (book (publisher "Apress")
                 (title "Programmer’s Introduction to C#")
                 (author "Eric Gunnerson")
                 (publication-date "2001-06-30")))

The S-expression is trivially parseable; the XML, OTOH, requires a fairly complex (hence potentially buggy and insecure) piece of software — and if you’re not careful, you’re susceptible to a billion-laughs attack. The XML will be littered with extraneous text elements between the tags; the S-expression is not. The S-expression just has atoms and lists; the XML has both tags and attributes. Why is publisher an attribute while title is a tag? Who knows?

It’s probably not a coincidence that a Google search for "well-designed XML" yields very few results, with your comment one of those few.