Most of the stuff in this article is superficial stuff that I don't think matters. What the article seems to describe are practices that generate consistent, p

Most of the stuff in this article is superficial stuff that I don't think matters. What the article seems to describe are practices that generate consistent, predictable RESTful APIs, which is exactly how you yield easy to use APIs. This saves both the creator and consumer's time, as debate and decisions over deviations are avoided. I'm not quite sure why so many comments have gone so negative -- this is hardly a revolutionary piece, yet many of us are creating or dealing with APIs that could do well to take some advice.