https://htmx.org logo
Powered by
# htmx-general
  • m
    i am a stubborn man
  • m
    we shouldn't issue multiple requests from the same element, it should queue and then issue the next request when the first one finishes
  • s
    ya but the issue is that the data in the supplied ctx element is ignored.
  • q
    So really no easy solution for now, right?
  • s
    ok, I thought you support IE11 because of empathy.
  • m
    unfortunately not right now
  • m
    can you open an github issue w/ more... er... context? šŸ™‚
  • m
    sufficient levels of stubbornness are indistinguishable from empathy
  • s
    ill try to make a proof of context .. err .. concept issue and see if i can replicate on apublicly availible page
  • f
    Just did some digging, and MSIE 11 share is very, very low. e.g. https://en.wikipedia.org/wiki/Usage_share_of_web_browsers - perhaps 1.x continues to support MSIE11 and 2.x moves forward? Ten year window seems plenty. šŸ¤·ā€ā™‚ļø
  • m
    added the 
    intersect
    pseudo-event to htmx: don't use if you want to support IE11 šŸ™‚
  • m
  • m
    will do something similar for using the 
    template
    tag for parsing server responses (you will need to opt in for that via the config)
  • s
    I created a list of JSFiddle examples on github. Pull-Requests are wellcome! https://github.com/guettli/htmx-jsfiddle-examples
  • m
    Has anyone used Hotwire?
  • a
    Hello Everyone! I have some questions. I'm not a frontend guy. I want something easy to use to start learning. QUESTION, is htmx a replacememt of Alpine JS? Can they work together? Do they do different things? They complement each other? Thanks for the help šŸ˜‹
  • a
    cool
  • m
    Htmx and alpine play well together. Htmx has a well developed event model so you can hook into that using alpine quite easily. Hyperscript is a more direct competitor w alpine but I view it more as a replacement for jquery
  • m
    Htmx is geared toward client/server interaction whereas alpine is for front end scripting, so different and complementary focuses
  • p
    This is great, thank you
  • p
    Yeah I've found very few problems using htmx with alpine, they complement each other very well - especially if you want to keep all your JS inline & avoid a build step
  • m
    Why use htmx when Hotwire exists?
  • m
    why use hotwire when htmx exists?
  • m
    why use either when react exists?
  • m
    why use any of those three when vue.js exists?
  • m
    why use any of the four, when livewire exists?
  • m
    and, frankly, why use anything when lisp exists?
  • m
    Because Hotwire makes it seem like you get everything from web to native
  • m
    Turbo uses complementary techniques to dramatically reduce the amount of custom JavaScript that most web applications will need to write: Turbo Drive accelerates links and form submissions by negating the need for full page reloads. Turbo Frames decompose pages into independent contexts, which scope navigation and can be lazily loaded. Turbo Streams deliver page changes over WebSocket, SSE or in response to form submissions using just HTML and a set of CRUD-like actions. Turbo Native lets your majestic monolith form the center of your native iOS and Android apps, with seamless transitions between web and native sections.
  • p
    That's pretty much copypasted from the Hotwire page. There are large differences in how they work, and choice of one over the other depends on your requirements and environment.
1...260261262...1146Latest