Earlier quoted context omitted.
Given the number of people claiming to be CEO of HTMX, I have to ask: what’s the joke I’m missing?
There is something here, but I am not sure if it's the whole story: https://htmx.org/essays/lore/
Htmx 4.0
81–90 of 217 posts
Re: Htmx 4.0
#82Re: Htmx 4.0
#83Strange. The picture of the jeep looks similar to the Omarchy Quatro Desktop wallpaper. Is there a connection? How come both look so similar?
Re: Htmx 4.0
#84Re: Htmx 4.0
#85Re: Htmx 4.0
#86Re: Htmx 4.0
#87For pushing updates, we use ActionCable, but we do it in a different way from what we used to do with Turbo Streams: when a record is updated, instead of sending HTML from the server to the client with instructions on what to replace, we only send a small JSON payload with the ID of the element that was updated. On the client side, an event is dispatched that any DOM element with :updated from:body"> will trigger on. For the rest it's just basic HTMX, only the trigger is "custom".
Re: Htmx 4.0
#88I really like htmx, and intercooler.js before it. It's been a while since I tried to convince a co-worker to use it, it might be time to try again. Either way I can't wait to try out the new version. Full Disclosure, I am CEO of HTMX
> Full Disclosure, I am CEO of HTMX
i think you've found a good job!
Re: Htmx 4.0
#89Re: Htmx 4.0
#90Before vibe coding was a thing, HTMX made it super easy for me to implement Ajax like features. It was the most approachable library I've ever seen, and I'll always be grateful for it.
What about vibe coding makes HTMX something that you speak about in the past tense? Are you just generating frontends in vanilla JS now?