Fuck XML. Fuck it right up it's X with it's M, all the way to L.

*laughs in JSON*

Who still uses that? :D

@kpenc more than you think, not always JSON is the best solution

@kpenc "Enterprises"

Our crm does some really crazy impressive stuff with xml. It works for us pretty well.

Although xpath is a chore, so I see your point.

As a previous Java developer I support of this message. 😂
XML was made for machine yet humains have to read it ugh.

Do you configure Spring with XML or in your Java code...? Both? Good thing I have no longer to deal with this.

The "if else" in xslt is the most horrible thing ever: ITS NOT "IF ELSE" BUT "CHOSE WHEN OTHERWISE" FUCK STANDARDS.

@dontbeevil give me an example. :)

@kpenc

JSON
Pro:
Simple syntax, which results in less "markup" overhead compared to XML.
Easy to use with JavaScript as the markup is a subset of JS object literal notation and has the same basic data types as JavaScript.
JSON Schema for description and datatype and structure validation
JsonPath for extracting information in deeply nested structures
Con:
Simple syntax, only a handful of different data types are supported.

XML
Pro:
Generalized markup; it is possible to create "dialects" for any kind of purpose
XML Schema for datatype, structure validation. Makes it also possible to create new datatypes
XSLT for transformation into different output formats
XPath/XQuery for extracting information in deeply nested structures
built in support for namespaces
Con:
Relatively wordy compared to JSON (results in more data for the same amount of information).

interesting reading if you want know more
http://yegor256.com/2015/11/...