I remember when XML first came out. No really, I do. I made a half-hearted attempt to learn it before I lost interest.
Let's just say it was one of many bad career decisions.
So, I'm feeling pretty darn old today after reading Joe McKendrick's latest column, which raises this horrible question, "Has XML already become a (gulp) legacy mark-up language?"
My gut response, "Well, I hope not. Because I'm just not emotionally ready for that."
McKendrick's question was prompted by a recent blog post by Ganesh Prasad, an Australian software architect who works in the financial services industry. Prasad builds his assessment on the appearance of JSON, then JSON Schema and, more recently, Orderly, which he describes as a "a new schema language developed by Lloyd Hilaiel, a software engineer with Yahoo, that is far more compact than JSON Schema and yet round-trips to JSON Schema quite effectively."
Prasad argues that Orderly will free up SOA architects to recommend the "simpler JSON data format instead of XML without having to worry about the lack of rigour in data definition."
McKendrick's post also notes that Ganesh isn't the first one to raise the possibility of XML's demise, noting that TechTarget's Jack Vaughan made a similar case in October.
I suppose I should've seen it coming when I wrote about XML's 10th birthday-three years ago. Still... even three years ago, JSON existed, and yet, as McKendrick notes, XML remains "the foundation of many integration efforts, Web services, and SOA projects, so it's not going away anytime soon."
And, as Mike Vizard recently pointed out, there are still signs that XML could finally reach its unfilled potential. Although, he also suggests that it could be that IT has gone as far as it can go with XML.
Sigh. Que sera, sera. Until we know for sure, I'm going back into denial about XML's age...and my own.