</> 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
  • HubertManne@moist.catsweat.com
    18·
    1 month ago

    This is sorta funny for me because as a non cs major who went into it it seems like all the api’s I work with are called rest apis and I was always wondering what a non rest api would be.

      • wizardbeard@lemmy.dbzer0.comEnglish
        11·
        1 month ago

        Hahaha, don’t underestimate jank ass vendor systems. My workplace has at least one business critical thing using SOAP. We’ve been spinning our wheels on deprecating the damn thing for three years.

        • Rikudou_Sage@lemmings.world
          1·
          25 days ago

          Our government a few years ago made a cool new system to sniff on small businesses because they don’t have enough money to defend themselves properly in court track cash transactions and it was so hip and new that it used SOAP. That was the first* time I worked with SOAP, until then I managed to avoid it.

          * I technically worked with SOAP once before but the part I worked on was like ten abstractions away from the protocol.

      • HubertManne@moist.catsweat.com
        2·
        1 month ago

        see. now I have seen references to soap but never really got that to. when it comes down to it my biggest concern is things just work.

  • vzq@lemmy.world
    169·
    1 month ago

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

    Interesting historical note, but things change.

    • Dunstabzugshaubitze@feddit.org
      251·
      1 month ago

      I’d Agree in most cases, but not in this one.

      Rigor in definitions allows us to express a lot of complex things in a compact form. this allows us to treat “Cars” as something different than “Motorcycles” while both a motorized vehicles.

      the same is true for REST-API and other API-Types, while all of them are just a means to allow services to exchange data, they tell us a lot about how this exchange happens and what to expect, but only if we use the words in a way that they represent the concept they were meant to represent. Otherwise we end up with meaningless buzz words like “rest”, “agile”, “scrum”, “artificial intelligence” and so forth, instead of meaningful terms found in the jargon of other engineering disciplines like “magnetism”, “gravity” or “motor”.

      • frezik
        232·
        1 month ago

        We’re well past that. I would probably care more if the original idea behind REST solved a real problem, but it doesn’t. It’s architecture astronaut stuff.

        If REST is just about using HTTP verbs and status codes smarter, and sending the payload in JSON, I’m good to leave it at that. It’s useful.

        • vzq@lemmy.world
          17·
          1 month ago

          Besides, the original definition is not reflective of real world needs - which is why it’s morphed to something else.