So the author proposes to replace REST with "JSON-pure APIs": Just stuff all of your data (errors, warnings, data, domain-specific stuff; he really does not propose any structure) into JSON, and then send and receive that via anything.<p>With this, we would lose the discoverability of a good REST API (see <a href="https://en.wikipedia.org/wiki/HATEOAS" rel="nofollow">https://en.wikipedia.org/wiki/HATEOAS</a> ), which would be a huge price to pay.<p>Other than that, this reminds me a bit of:<p>"Hey man, this relational stuff is really hard! There must be a better way..."<p>"I know a better way! Let's rather just stick all of our data into these JSON objects..."
When it comes to APIs, every now and then someone say "X is dead, Y is the future".<p>APIs are not a one-size-fits-all problem, and while general trends and paradigms are a nice thing to have, developers should not be restricted by whatever is the hottest buzzword today.<p>A nice and clean API will always be pleasant to use, and this has nothing to do with RESTful awesomeness or SOAP verbosity.