Other, like OP, think REST isn't going far enough in that HATEOAS is what "really" makes something restfull. This doesn't really work in practice as if changing the schema of some JSON response can magically change the behaviour of an application. I you want to lift all the logic to the server, I guess you can use htmx, but then you are not building an api anymore but a remote rendering engine.
https://htmx.org/essays/hypermedia-apis-vs-data-apis/
REST was coined to describe the web. It has been misapplied to JSON APIs over HTTP, and the way we got here is a funny story:
https://htmx.org/essays/how-did-rest-come-to-mean-the-opposi...
other related essays:
https://htmx.org/essays/hypermedia-clients/
https://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans.h...
It’s like human languages: REST is whatever we make of it, regardless of what academics say.
This keeps happening and all it does it cause confusion.
It's one thing to make up new words for new concepts so you can more easily refer to them in a conversation.
It's another thing entirely to give a word a vague but similar meaning without any clear way to differentiate between the original specific and new extremely nebulous concept.