Remember the heyday of Web services, when we were always just one specification away from perfect interoperability? Ultimately, that towering stack of protocols collapsed under its own weight. SOAP and XML generally are ridiculously verbose protocols that began with a commitment to simplicity and gave way to mind-numbing levels of complexity. Add to that the service repository mess: UDDI died an ignominious death, and OASIS's S-RAMP committee can't even create a website that isn't all broken links.
I remember evangelizing REST+JSON for certain applications and even teaching a class on the subject back in 2009-2010. Many were reluctant, to say the least, but now everyone is jumping on the bandwagon because it's "easier" than SOAP. Great, but the problem is that they are often still doing it wrong. I've seen some pretty unRESTful RESTful applications in the past few years. It would be nice if some of these people would read Fielding's paper or at least a book on the subject before creating some monstrosity that someone like me will eventually have to come in and redesign/rework.
This post has been edited by Programmist: 26 January 2013 - 01:46 PM