https://htmx.org logo
Powered by
# htmx-general
  • m
    1) yes, it's a slippery slope and you have to work to ensure that you are using htmx in a progressively-enhanced manner if that's what you want. Some patterns (e.g. lazy load) simply won't work without javascript 2) Yes, you are understanding it correctly. htmx is more manual and low level than hotwire, attempting to build up from HTML rather than provide a total, transparent solution. 3) you can use any sort of valid 
    hx-swap
    value (e.g. 
    beforeEnd
    ) for `hx-swap-oob`: https://htmx.org/attributes/hx-swap-oob/ Again, you will find it more manual than hotwire
  • l
    1) Sure. But that’s kind of what I’d like to get to: keep the bare bones working without JS enabled but get all the niceties if enabled. Without lazy loading, the anchors could at least be followed manually. Ugly, but functional. 2) I wasn’t really judging. I’d just like to wrap my head around the approaches. I like the idea of sticking all of this to attributes and not add additional elements. It’s a different level of hiding things but that also makes it harder to understand what’s actually going on. 3) Ah, I missed that, nice! Doesn’t even feel “more manual” but rather sticking the info to the original element rather than wrapping it.
  • m
    Yep, no offense taken. Both are valid approaches and hotwire is a great library. htmx comes at things from a lower level, so maybe a bit more work at times, but maybe a bit more flexible as well.
  • l
    Although for 3), the approach is slightly more demanding to the template engine rendering the fragment as it needs to be able to add attributes to the root element of the fragment.
  • e
    This was a great talk! As someone that didn't touch computers until well after web 2.0 came around, the history presented was quite insightful 🙂
  • m
    🙂 that's fantastic to hear. It really is a shame that the thought leaders who pushed REST in JSON APIs (e.g. https://www.martinfowler.com/articles/richardsonMaturityModel.html) never went back to reexamine the concept. It all makes a ton more sense in terms of hypertext. Maybe the tides are turning...
  • b
    i want to use "window.location.href" but how to do it in htmx? I found a reference "HX-Current-URL" but I don't know how to use it. can you tell me. thank you for helping
  • b
    Can you please explain a little bit more your use case please? When exactly do you want to redirect the user? Upon which event?
  • b
    i want get current URL with htmx like this . --> https://jsfiddle.net/62qsr50d/ can it be done with htmx?
  • m
    it looks like you are doing this in hyperscript, not htmx. In which case you can say something like:
    Copy code
    set url to the href of the window's location
  • m
    thank you @User for your work on pulling SSE and Websockets out to extensions!
  • g
    Any interest in making hx-boost an extension?
  • b
    Thanks, I will try
  • m
  • m
    REST or RPC?
  • g
    you know what we really need tho? elm, but for everything
  • g
    oh come on
  • g
    who doesnt like friendly error messages?
  • m
    \> event driven systems \> no error messages at all \> because nothing happens \> because the event was named something else or was dispatched somewhere else in the DOM
  • m
    😑
  • g
    😅
  • g
    obviously no faults / no obvious faults
  • g
    also while we are at it, lets get rid of the DOM
  • g
    and just raw dog that web dev shit
  • m
    really, if you think about it, jump and link was a mistake
  • g
    DOM was a mistake
  • g
    virtual memory and its consequences...
  • g
    remove DOM, make lists(?)
  • m
    car cdr, who needs anything else?
  • g
    idk are there any real alternatives to DOM tho
1...406407408...1146Latest