there is a growing reaction against the JS-everywhere situation, using hypermedia & HTML over the wire rather than JSON data APIs I am calling these applicatio

there is a growing reaction against the JS-everywhere situation, using hypermedia & HTML over the wire rather than JSON data APIs I am calling these applications Hypermedia Driven Applications or Hypermedia Oriented Libraries: https://htmx.org/essays/hypermedia-driven-applications/ https://htmx.org/essays/hypermedia-driven-applications/ libs like unpoly, hotwire or my own htmx are all hypermedia oriented, recentering HTML and hypermedia as the core application architecture for your app some other related essays: https://htmx.org/essays/spa-alternative/ https://htmx.org/essays/spa-alternative/ https://htmx.org/essays/a-response-to-rich-harris/ https://htmx.org/essays/a-response-to-rich-harris/ the really nice thing about the hypermedia approach is that it takes pressure off adopting JS/TS on the backend, since you no longer have a massive front end codebase already in JS/TS and it can be hard to justify having two different languages, models, etc. With hypermedia, you don't have this situation. I jokingly call this "stack" the HOWL stack: Hypermedia On Whatever you'd Like.