https://htmx.org logo
Powered by
# htmx-general
  • m
    Got it thank you.
  • m
  • m
    Looks great man do they have a discord?
  • s
    You nailed it. You say "just works magic". And that's something that I don't like. I don't like magic. I want things to be simple and obvious. I looked at the Hotwire docs, and I only saw marketing blabla. Then I looked at the htmx docs and understood immediately what it is about. That's why I took htmx.
  • s
    @User could you please tell me how I could simplify this jsfiddle by using hotwire instead of htmx? https://jsfiddle.net/thomas_guettler/tgp1u0qf/
  • s
    @User "partial refreshes" that's it. Sounds better than "html fragments over the wire". I will meditate on this during the next days. ... I think the first sentence on htmx.org could get improved. For example: I don't care at all about web-sockets. Some do, some don't. I think the term "partial refreshes" should be part of the first sentence.
  • p
    Having used both, the high-level difference is that Hotwire requires more server-side integration to handle different drive/stream/frame responses - with htmx you might need to get/set some headers in certain cases, but it's much easier to drop into an existing project and introduce gradually. Htmx also has a much richer set of options. If you have a turbo plugin in place (e.g. with rails) turbo drive (i.e. the old turbolinks) is very easy to get started with and works pretty well, but hx-boost is quite close in functionality. Again really depends on what your needs are.
  • p
    technical considerations aside, turbo is very much still a rails thing and its future is uncertain given recent problems. I remember that the old turbolinks/stimulus went for years without much communication and updates, so overall I wasn't too happy with the OSS stewardship of these projects. Htmx has wider adoption (i.e. used by people from many different backend frameworks) and @mysterious-toddler-20573 and others do a great job in managing the project, addressing issues and communicating with users.
  • p
    If I was evaluating an "html-over-the-wire" solution as part of a production project, htmx would be an easier sell on these considerations alone.
  • q
    > turbo is very much still a rails thing and its future is uncertain given recent problems. I feel that I am not informed well enough. Could you please explain, what is this about?
  • p
    tl;dr; Hotwire was developed by Basecamp as the next generation of Turbolinks to support its new Hey email service. There were a large number of resignations from Basecamp last month (the reasons aren't worth regurgitating here: you can Google them). Among those leaving were the developers of the Hotwire stack (Turbo/Stimulus) who have also declared they will no longer be working on OSS projects related to Basecamp.
  • m
    Hotwire is full stack
  • g
    freenode is dying 😦
  • g
    end of an era
  • g
    hopefully the replacement gets traction
  • g
  • m
    htmx is explicitly not full stack: we are trying to extend HTML as a hypertext, and be back end agnostic (you change your back end as little as possible)
  • m
    it's a different approach and is more explicit in what you want to have happen, which is what I mean when I say hotwire is more magical
  • m
    that said, you seem really pumped on the hotwire approach, and it seems like a great way to build web apps so we all wish you luck in your endeavors
  • m
    if they don't have a discord yet, maybe you could start one
  • m
    bummer, seems like a lot of folks are having a tough time getting along these days
  • g
    it's not a personality thing, it's a hostile takeover by a foreign actor.
  • m
    ugh, even worse
  • m
    I use private internet access too 😦
  • m
    what should I switch to?
  • m
    should I switch?
  • g
    idk much about PIA/vpns in general
  • g
    i only use one when i have to
  • a
    Thanks. This clarifies a lot. Maybe add a FAQ in the docs?
  • g
    Recruiting opportunity?
1...262263264...1146Latest