Parse Releases Their REST API (opens in new tab)

If you say you've written some very RESTful APIs internally, perhaps writing an article about the things you've specifically done from most APIs that makes yours RESTful and advantageous vs. a less RESTful API.

I upvoted you.

I would like to learn how to do REST "right", and (for me) it's easier to learn by playing with a working example that deals with "real world" issues as opposed to abstract snippets that only show how APIs get used.

Any further insights/examples/pointers would be greatly appreciated.

Subbu Allamaraju (ex-Yahoo, now eBay) has been the one proponent of REST that I believe speaks the most sense.

He understands that most "RESTful" APIs out there leave HATEOS as an afterthought, but he doesn't believe there is such a thing as a 100% RESTful API - you match the architectural style to the context of the problem you are trying to solve.

http://www.subbu.org/

Twilio is pretty close.

Are you saying Roy Fielding is like Humpty Dumpty? If so this doesn't appear to be a very useful or enlightening comment.

That reminds me of what happened to "Object Oriented". First, Alan Kay coined the term, having something like Smaltalk in head (emphasis on messages, and a strong dislike of unchecked side effects like setters and the assignment statement). Then the term was subverted, and we got C++ and Java (emphasis on classes, and a near-total disregard for the problems of pervasive side effects[1]).

My point is, we should be careful before we corrupt a term. Doing so corrupts our perception of the concept itself. And if it turns out the corrupt concept is less help than the pure one, too late : it's already popular.

[1]: That assignment thing really sucks: http://www.loup-vaillant.fr/articles/assignment

Your argument appears to be unconcerned with truth, wisdom or understanding.