hot take i will absolutely not stand by in a few hours
xml is actually great, both to read and write, by humans and machines (at least as a subset of xml).
i kinda miss having xml everywhere
json awful to write and unreadable without indentation (counting the ]} )
yaml is far too complicated and intuitive for what it achieves
toml is nearly that but it's too flat, it's just not the same
@Sylvhem @CobaltVelvet tbh I don’t think one is significantly better or worse than the other. I tend to like JSON better because it’s less typing/lighter but XML is a decent choice in my cases too.
@melunaka I think I would definitely be less salty about JSON if it wasn't pushed that hard by so many people.
@CobaltVelvet ok, I see your take and counter by mentioning SOAP
@szbalint @CobaltVelvet ironically SOAP has to be among the dirtiest (mis)applications of XML out there. #RESTisbest
@CobaltVelvet For JSON, the solution is to use jq, for pretty-printing.
@bortzmeyer i never remember the parameters to make it work nicely with less
jq "." | less
@bortzmeyer jq "." -C | less -R 😉
@CobaltVelvet Also, XML came with a lot of actual standars to work with it. XML Schema, XSLT, XPath, (XHTML), ...
@CobaltVelvet Also, XML is easy to grasp if you're not à developper. JSon is really obscur if you don't know JavaScript.