[_heimdall]

> There is a reason why HATEOAS is almost never observed in REST setups.

I saw the HTMX creator floating around the thread so hopefully he can confirm, but my understanding is HATEOS is a specific implementation of a REpresentstional State Transfer API. JSON is often used for the API, HTMX uses HTML instead but it is indeed still a REST API transferring state across the wire.

My shift key really doesn't appreciate all these abbreviations

[recursivedoubts]

REST is almost always a misused term:

https://htmx.org/essays/how-did-rest-come-to-mean-the-opposi...

HATEOAS (or the hypermedia constraint) is a requirement for a REST-ful system, as the creator of the term (Roy Fielding) says here:

https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypert...

I have an rewritten wikipedia article on HATEOAS here:

https://htmx.org/essays/hateoas/

And I agree it doesn't make much sense outside of a hypermedia system (like the web), being consumed by humans:

https://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans.h...