4 ms·

Sounds pretty slow. At least a second before the UI responds to any action?

• berkle4455 4y ago
  What sort of slow backends do you work with? My PHP htmx application responds in ~30ms including network transmit. Even if you’re across an ocean it’s maybe 300ms.
  • b4je7d7wb 4y ago
    300ms feedback on user action is unacceptable. But I read another comment saying there can be loading indicators so in that case its fine.
• BizarreByte 4y ago
  It’s much faster than that in practice, but of course it comes down to how well your backend is written. I’ve been using HTMX lately and I can blink and miss the UI updates. I wish I had numbers, but in my experience it’s far better than you’d expect. Basically take the length of a REST call you’d have to make anyway and add a few milliseconds for the rendering. It won’t be the right choice in all cases, but it’s a great option in many.
  • throwawaymaths 4y ago
    It seems such a waste... You're chucking all that cryptography (ssl, encrypted cookies) away only to be redone every. single. Dom change
    • deleted 4y ago
      [deleted]
    • movedx 4y ago
      Huh? How does HTMLx "chuck" away SSL (you meant TLS, right? I hope you're not using SSL) and encrypted cookies? How about you try it and see?
      • devin 4y ago
        It’s fine to use SSL interchangeably with TLS IMO. It’s still called OpenSSL.
        • movedx 4y ago
          I suppose, but it's not really that big of an effort to just use the correct term for the correct version of the technology.
          • throwawaymaths 4y ago
            The certs are generally called SSL certs, not tls certs, too.
            • movedx 4y ago
              > AWS Certificate Manager - Provision and manage SSL/TLS certificates with AWS services and connected resources Both, I guess.
      • throwawaymaths 4y ago
        By chuck away I mean all those processor cycles to perform cryptographic verification... And then throw away the result because you have to do it on the next connect anyways And I have written a library that does the full SSL handshake/upgrade cycle off of tcp sockets, and managed my own private CA, so I'm not a total idiot.
        • dan1234 4y ago
          Isn’t that mitigated with TLS session resumption and TLS 1.3’s 0-RTT?
        • kaba0 4y ago
          How is that different than all the other CSR SPAs that do a REST call on every button press as well? They do almost the same amount of work, and will also “throw away” the results.
  • amelius 4y ago
    > but of course it comes down to how well your backend is written Also the latency of your connection matters.
    • BizarreByte 4y ago
      I thought frontend devs stopped caring about bad connections years ago? ;) HTMX is fine with showing loading icons are the like if needed, but yah, connection latency is going to have an effect.
• silver-arrow 4y ago
  You for sure wouldn't want to build a spreadsheet type app with htmx because of that aspect. Many other types of web apps can benefit from the simplification of the architecture, however. And like my paging example, many times you need to go to the server anyway. But sure, like anything, I wouldn't use htmx for every situation.
• silver-arrow 4y ago
  True BizarreByte. I love how htmx let's you easily add animation indicators on actions, because many times it's too fast due to the small chunks coming back and getting placed so quickly in the DOM
• mixmastamyk 4y ago
  Same as a javascript round trip. Can still make local-only changes if you'd like.