3 comments

[ 0.23 ms ] story [ 17.5 ms ] thread
In my opinion - JSON won. It is much more relevant today than XML.

If anyone want to use the domain JSON.Com or NoSQL.Com for a similar project as Tim Bray - let me know.

There isn't any winning or losing here though - it's horses for courses. There's no way you could sensibly author complex technical documentation in JSON, for instance - and I'd contend there's precious little reason to these days, when the two formats can be treated more or less interchangeably (at least with the right tools).
Relevant to what? Use the right tool for the job. Did all carpenters turn in their hammers when the air-powered nail gun appeared? Of course not. Likewise, should everybody stop using XML because of JSON? Of course not. The important thing is to understand the strengths and weaknesses of all the various technologies we use and use the right ones as needed to achieve the goals at hand.