So what do you call a system that uses more than two HTTP methods (e.g. uses PUT and DELETE as well as GET and POST), and has marginally-more-human-readable URLs, but doesn&#x27;t send self-descriptive representations, doesn&#x27;t use hypermedia, doesn&#x27;t Transfer REpresentational State, and probably also isn&#x27;t stateless?<p>I mean, statistically speaking, if you have such a system, my bet is that you call that system RESTful.  Furthermore, if you have such a system, you vastly outnumber the people building systems that obey Fielding&#x27;s constraints.  So in practice, you win the argument about what &quot;RESTful&quot; means.<p>Can we please stop legitimizing Rails&#x27;s whimsical aesthetic choices by pretending that they have something to do with an academically-justified architecture, and just accept that they&#x27;re just another way of ripping your denim and then safety-pinning it closed, by which you demonstrate that you&#x27;re not a square and you don&#x27;t write Java.