</> htmx ~ How Did REST Come To Mean The Opposite of REST?
htmx.org
htmx gives you access to AJAX, CSS Transitions, WebSockets and Server Sent Events directly in HTML, using attributes, so you can build modern user interfaces with the simplicity and power of hypertext htmx is small (~14k min.gz’d), dependency-free, extendable, IE11 compatible & has reduced code base sizes by 67% when compared with react
  • Fred@programming.dev
    0·
    1 month ago

    Maybe I’m wildly misunderstanding something, not helped by the fact that I work very little with Web technologies, but…

    So, in a RESTful system, you should be able to enter the system through a single URL and, from that point on, all navigation and actions taken within the system should be entirely provided through self-describing hypermedia: through links and forms in HTML, for example. Beyond the entry point, in a proper RESTful system, the API client shouldn’t need any additional information about your API.

    This is the source of the incredible flexibility of RESTful systems: since all responses are self describing and encode all the currently available actions available there is no need to worry about, for example, versioning your API! In fact, you don’t even need to document it!

    If things change, the hypermedia responses change, and that’s it.

    It’s an incredibly flexible and innovative concept for building distributed systems.

    Does that mean only humans can interact with a REST system? But then it doesn’t really deserve the qualifier of “application programming interface”.

    • ramble81@lemm.ee
      0·
      1 month ago

      It feels like he’s trying to say something like Swagger should always be required. One of the things about SOAP for example was that it always had a self-generating WSDL that you could consume to get everything. There were quite a few REST endpoints that were missing this when first developed.

      But I do agree that “forms” and “html” are quite the opposite of an API.