</> 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
  • @vzq@lemmy.world
    10•3 days ago

    This is all very “old man yells at cloud”.

    Interesting historical note, but things change.

  • @freagle@lemmygrad.mlEnglish
    5•3 days ago

    Honestly this is completely ridiculous. Hypertext using HTML constraints is absolutely insufficient for representing application state. It’s the wrong tool for the job and always has been, because it conflates document structure with semantic meaning.

    Said another way, HTML cannot be relied on to capture a representation of application state.

    The reason REST doesn’t use HTML in most contexts is because applications don’t use HTML in most contexts anymore.

    Demanding that application representation use a specific encoding strategy is ridiculous and misses the point entirely, which is that HTTP is no longer the right protocol for the job.

    • @Kissaki@programming.devOPEnglish
      1•2 days ago

      They’re not demanding anything. They’re describing how the current meaning of REST is nothing like the original one.

      They’re making a point for not splitting application state and logic into client and server with shared knowledge. If you’re making that a pretext of course their argumentation won’t fit. They’re describing an alternative architecture and approach. Not an alternative protocol for the current common web application architectures.