I totally agree with you, that it would be wrong to condemn XML. As you mentioned, it might be hard to start with, but after that tough beginning all of what you wrote in favor applies.
However, I've worked with large XML files and the tooling (at least in Java) is everything else but fun. Stream parsing using SAX might be okay, but as I also wanted to transform large files using XSLT (which was a real pain to write btw) in a streaming manner, it took a lot of custom code to get that done.
Unfortunately, the alternatives are indeed not even better. For JSON there is at least JSON Schema. But I don't think, there is something like XSLT for JSON Schema, is it?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I totally agree with you, that it would be wrong to condemn XML. As you mentioned, it might be hard to start with, but after that tough beginning all of what you wrote in favor applies.
However, I've worked with large XML files and the tooling (at least in Java) is everything else but fun. Stream parsing using SAX might be okay, but as I also wanted to transform large files using XSLT (which was a real pain to write btw) in a streaming manner, it took a lot of custom code to get that done.
Unfortunately, the alternatives are indeed not even better. For JSON there is at least JSON Schema. But I don't think, there is something like XSLT for JSON Schema, is it?