>You're going on about the value of "conventional methods" in a criticism of using HTTP verbs? Yes? These have some intrinsic value that is defined in the doma

>You're going on about the value of "conventional methods" in a criticism of using HTTP verbs? Yes? These have some intrinsic value that is defined in the domain. There is no potential of vocabulary contamination because everyone comes into the domain with a clean state. An ambiguous, abused common vernacular is worse than a clean domain-specific one. >Understanding the difference between a GET and a POST isn't some new-fangled idea, it's decades old. Like Tim Berners Lee old. GET and POST usually work out OK; it's stuff like HEAD, PUT, and PATCH that people usually argue about, not to mention response codes. GET, POST, and the HTTP intricacies are fine as a concern for HTTP clients. REST has shot through that and made it something that everyone has to worry about. The issue is not only that no one can agree on how to do REST, but it's also, as stated in my other comment, that REST makes it harder to see what's going on. It requires important information (the verb) to be tucked away into something that takes extra steps to access. I'm not saying it's impossible to access that; I'm just saying it's error prone to do it this way. >I didn't even know what Thrift was until I Googled it, and found out it was developed at Facebook. Okay. I hate most "Project-By-BigCo" projects, but not everything that comes out of Google or Facebook is automatically evil. Thrift is now controlled by the Apache Foundation, not Facebook. And it's a very common IDL, but I'll refrain from returning your snark. ;) >I'm stunned. Do you write code that runs on the internet? I'm not the only one. [0] >How did you even get employed? Just lucky I guess. [0] https://twitter.com/skamille/status/588713316358475776 https://twitter.com/skamille/status/588713316358475776