> why the htmx approach has more benefits over the HATEOAS approach of something like API Platform that I linked to My understanding is that HTMX is based on t

> why the htmx approach has more benefits over the HATEOAS approach of something like API Platform that I linked to My understanding is that HTMX is based on the HATEOAS approach: https://htmx.org/essays/hateoas/ https://htmx.org/essays/hateoas/ About API Platform you linked to, the homepage is not very clear (full of buzzwords but little info) but it appears to be a Backend+Frontend framework/distro based on PHP+JavaScript. Compared to that, HTMX is an HTML extension (just additional fields in the markup) which any backend/frontend can implement: even web browsers which don't have a JS runtime could implement HTMX and that's pretty cool. > I mean proprietary as in proprietary to htmx I believe HTMX is free software and i don't see a reason the specification can't be implemented by other projects. It's therefore not proprietary in my definition of the word. > something that ties your APIs to markup rather than using an interchange format such as JSON HTML/XML isn't that different from JSON. Just like your markup can evolve with your data structures and use-cases, so can your JSON. If you want interoperability, you should probably be using XML/JSON schemas and API versioning.