Yes, the REST approach is very cool… but maybe not so usable.
You can POST things, and later PUT your changes, GET the result and then DELETE it.
Perhaps I’m missing something, but what if you have disabled JS on your browser?
You can’t delete nor update! And this sounds no good…
You really need to make your site suitable for non-ajax users while requiring them to be JS-enabled??
So where does go that few less “pain in the ass” (DHH words) while making our application for ajax and not-ajax users?
One last thing: is REST an acronym? and if not why it’s uppercase!
I hope it’s clear enough, and I’ll be happy to be wrong. Do not misunderstand, I’m not the Java-guy-of-complaints, I’m a proud rails developer.