What Happend To HATEOAS in RESTful API? | Pre HTMX

In this video, I wanted to understand what happened to hypermedia and why most REST apis no longer adhere to its constraints.

Do you think that HTMX is changing what it means to be restful again?

Music:

[OkyCapriatto]

The content and animations are amazing. They are very illustrative!

[phoneywheeze]

i think it's because of SaaS / API based business models. If you're returning html, it would be difficult for other applications consuming your api.

[gyurilajos]

HTMX is on the right path for sure. If you get your concept right software almost can take care of itself. After all software is a conversation and mutual learning symmathesy about intents and purposes amenable to effective articulation

[gyurilajos]

Nicely done. How long will it take to realize that the concept of application state transfer and REST itself was a bad idea that seemed to be a good to some at the time.Hypertext as the engine of Presentation of info structures and affordances for intentional intentinteraction and the resulting transformation in coherent workflows?

[kaleelmohammed]

Great content .. how do you make these animation presentations?

[arek]

HATEOAS isn't popular even in bigger APIs, when a client isn't a browser. I don't see how HTMX will embrace hypermedia, in a browser it's not necessary to show the structure of the resources.

[sauliustb]

the way it is explained here only points to a shift on where the knowledge is supposed to be. if hateoas provides all the details for the frontend, up to and including layout, there is too much work to provide different frontends for different devices. The common availability of JSON and JS frameworks makes it easier to share your api, without an api dev having to know every business detail to render a frontend. Maybe it is time to not use the word RESTfull anymore?

[luisgarciaalanis]

Cmon man! HTML verbs have been around since 1.0/1.1