The bottom line, from my experience is this: XML means you have to think about how you're architect information exchange much more thoughtfully, because XML is

The bottom line, from my experience is this: XML means you have to think about how you're architect information exchange much more thoughtfully, because XML is much more strict and follows very explicit rules. It also means you have to develop a schema for your interchange. With JSON, you can, more or less, just serialize as is, not much thought in the world, and it can be understood by the client. You're not obligated by the protocol to do anything about developing a schema or anything of that nature. Yes, parts of the XML world have now bled over (defined schema and path algorithms being the big ones I think) but they're optional for better or worse. Everyone takes the path of least resistance when given the opportunity at the end of the day. This is especially true of software engineers I've found.