While I think we all recognize that the approach, to handle data and not live objects, is different, you seem to have missed the core objections, which are that

While I think we all recognize that the approach, to handle data and not live objects, is different, you seem to have missed the core objections, which are that REST is and was widely misunderstood and FIOH might as well be the true protocol in widespread use today. The irony is that this 'REST' is used now in part to support lifecycle management of live objects, in the browser, but this has architectural implications. Further, dogged adherence to arbitrary 'REST' or FIOH explains the growing popularity of a growing number of non Restful http protocol extensions like websockets, webrtc, graphql, as people search for rpc alternatives for things REST was never intended for. This seems to be a pretty valid criticism of the state of industry 'REST'.