Jens Alfke, “commenting on the new Rdio API”:http://jens.mooseyard.com/2011/03/dudes-this-is-so-not-rest/:
“Maybe we should just give up on the term REST, since it’s become so diluted as to mean nothing more than ‘HTTP API that’s not as hard to use as SOAP’?”
Sounds right. “Pure REST”:http://en.wikipedia.org/wiki/Representational_State_Transfer was never strictly followed, and the advantage to consistent HTTP methods — being able to abstract parts of the client details away, as with “ActiveResource”:http://api.rubyonrails.org/classes/ActiveResource/Base.html — don’t seem like significant savings to me. Now that XML-RPC and SOAP are mostly dead, we assume that new APIs are going to be usable from any language without much effort. I won’t object to having one less acronym in the world.