> Chapters 1 and 2 focus on what hypermedia is and how a hypermedia system works.
Yes, they do. And they turn around, slap an "Extending HTML As Hypermedia" on it as if that sentence made any sense, and then keep on pretending what they do has anything to do with hypermedia.
> A hypermedia control is an element in a hypermedia that describes (or controls) some sort of interaction
> I think that's a pretty clear definition.
It's a string of words that make zero to no sense. What is an "element in a hypermedia"?
> htmx extends HTML as a hypermedia
This sentence also makes no sense
> making the set of hypermedia exchanges it can perform larger and more general.
Neither is true. HTMX limits all exchanges to HTML, and HTML only, and then clearly separates whatever HTML it accepts and "JSON Data APIs" into two separate entites. Doesn't make them hypermedia.
> but the philosophy underneath it is fairly well developed and, as far as I can tell, at least plausibly related to hypermedia.
But it's not. It's slapped on with al the confidence of a teenager who discovered a new word and now uses it everywhere.
Hypermedia isn't "we do REST requests and get HTML back" or "we separated HTML and JSON into two separate APIs, these are now hypermedia elements in hypermedia as we've extended HTML as hypermedia".
Just because you repeat something a hundred times, doesn't make it so.
They even mention HATEOAS a few times as if it had something to do with HTMX and literally throw it out of the window.
Edit:
They even completely misrepresented Roy Fielding's REST paper by pretending it only applies to HTML and claiming this somehow reflects the original idea behind the dissertation