Laughed most of the way through, but REST is really not the problem… It is developers who imagine their favored design pattern religion actually matters.
I like REST because I got tired of GETs changing state on the server side. By focusing URI schemes to describe resources (with nouns), not what is being done to them, we are forced to think a bit more thoroughly through what exactly we want to happen when an HTTP verb request comes in for a resource.
The only other thing I think you are missing is the reality of NoSQL… REST + JSON + Document-Oriented DBs like MongoDB mean the end of ORM. Literally thousands of lines of ORM code reduced to two! 1) Read the JSON string; 2) deserialize to your model.
And this is the origin of the idea you POST back the same structure you received in the corresponding GET. 1) Read a JSON string from your document oriented database; 2) deserialize it to your model; 3) operate on the data; 4) serialize your model with updated data back to JSON; 5) write the updated JSON document back to the DB.
You are certainly right about CURL and basic GETs to SOAP… and you point out that anything beyond that, with WSDLs being what they are, you’re stuck… With REST you can mock your models in simple JSON text files and use Postman to POST to your URI. Most tools (e.g. Visual Studio) will allow a local instance of the API and you can enter into it from Postman with break points.
Anyway… good laugh… to bad it was at the expense of what is a sound architecture… It was never meant to be a “standard” and the “standards” which have emerged around REST are just figments of the imagination of pocket protector types with delusions of grandeur.