Well, I somewhat agree... and I'm actually using the REST stuff for a valid business need in my current app.
But I will throw in here that:
- I still find map.resources hella confusing... map.connect was wonderfully obvious, simple, and powerful (though obviously one can still use it... I do)
- Not every interaction one will do with a server can be expressed as a noun. Ok, it probably can, but it will sometimes wind up being horribly forced... in a year you'll look back and say "wtf was I thinking!?!"
- The "resource" that the inventors of http envsioned was a *document*... not a "user" or a "post" or any of that. The document is the result of sending a request -- identified by a uri -- to a server, and the document, the same "resource" could be in a number of different formats... xml being one of them.
- Most importantly, it seems like there are a lot of people doing backflips to figure out "all this REST stuff" and fit it into their web app.... even when they have no immediate use for REST... or probably ever will. I firmly believe that REST capabilities should only be added when there is a need, not to be "cool and cutting edge".
b
PS: So when will acts_as_devils_advocate be available as a plugin? 
Jeff Pritchard wrote: