3 ms·
I'm on the otherside of the fence. HATEOAS just seems obvious, as in why would someone do it any other way. I recently wrote a client to spider legislation dat
by specialist 14y ago
I'm on the otherside of the fence. HATEOAS just seems obvious, as in why would someone do it any other way.
I recently wrote a client to spider legislation data published as WSDL. Were the reply/result documents HATEOAS, the spider would be trivial. But I have to basically do ETL between every reply and the next request (walking the children of a parent).
At the day job, some of the RESTful APIs (written by others) are mostly HATEOAS. It's a pretty big win. Clients are easier, inspection and verification is easier, non programmers almost kinda grok them, etc.