[alexpetros]

> HATEOAS would mean your browser/client would be entirely responsible for the presentation layer, in whatever form you desired, whether it's buttons or forms or pages or not even a GUI at all, such as a chat interface.

Browsers can alter a webpage with your chosen CSS, interactively read webpages out loud to you, or, as is the case with all the new AI browsers, provide LLM powered "answers" about a page's contents. These are all recontextualizations made possible by the universal HATEOAS interface of HTML.

[not_kurt_godel]

Altering the presentation layer is not the same thing as deriving it from a semantic API definition.

[alexpetros]

Altering the presentation layer is possible precisely because HTML is a semantic API definition: one broad enough to enable self-description across a variety of domains, but specific enough that those applications can still be re-contextualized according to the user's needs and preferences.

[not_kurt_godel]

Your point would be much stronger if all web forms were served in pure HTML and not 95% created by JS SPAs.

[sam_bristow]

I think the web itself would be stronger if it was served in pure HTML and not 95% created by JS SPAs.