XML is better because …
22 January 2007There is a war waging: do you want the trusted XML or the new JSON? Do you believe in Tim Bray or Dave Winer? Don Box or Dare Obasanjo?
Pick your REST now…
You might expect me to tell you to choose JSON just cuz I have a vested interest. But you would not be reading a blog about either of these technologies if you were dumb, so I give it to you straight:
- I have A LOT more experience with XML than JSON. So does EVERYONE! There are a lot more XML jobs now, but having JSON skills may be the deciding factor for your next interview
- XML has tons of kewl tools. On the other hand, it should be easy to get Altova to put a JSON validator into XmlSpy
- XML is already in Sql Server, Oracle, and other great databases. However, IMHO document centric information does not belong with relational data. Xml is probably going to stay in the DB, but there is NO reason JSON can be put on the server as well
- Xml has several schema definitions. JSON support now is mostly beta, but it is coded in JavaScript! That means YOU can change it.
- Xml has fantastic query capabilities with xPath 2.0 - However, they are all TRANSFORMATION languages. By using a JSON pathing language, you can define an evant driven model
- XML has some great client side libraries, but JSON is NATIVE to the client
I understand the problem: XML has so much behind it that you want to stay with what you know. XML is not going away. But neither is JSON - it is a GREAT idea (thanks Doug!) and will only continue to grow in support. Eventually each technology will fit a specific need.
So - who wins? YOU do!
One Response to “XML is better because …”
January 1st, 2008 at 11:39 am
You conclusion sums up the situation well…
We All Win.
In regards to point 3, this is where I hope we see the greatest amount of change for JSON, more DB support from all vendors.