so I don't mind special handling for it

your double-exec problem would be handled properly s/ a hx-head="reexecute" option

If head needs special treatment then that makes sense to not try and handle it as “just another tag” 👍

Thinking more on this: swapping multiple chunks of HTML, with multiple targets, possibly with multiple merge algorithms Is there currently a way to handle a single trigger kicking off multiple swaps? This makes me think of kicking off a pipeline/orchestration process. This may be way out of scope though 🙂

A bit out of scope, but I actually have a PR for something like that: https://github.com/bigskysoftware/htmx/pull/1096

hi I am new about the htmx library. I wanted to downlaod some sample from the site. But for example the "https://htmx.org/examples/value-select/" doesnt' contains the complete code.. Can anyone help me to undertand how manage it just to have an idea . thanks.

I've heard many SPA developers use this same excuse to build SPAs: > Hypermedia takes pressure off adopting a particular back-end technology

weird since SPAs are basically not production ready without server-side rendering of js components, which needs js to run on the server

thats... not true? SPAs can generally be built with any backend tech you want, why would you need a JS backend?

how would I do SSR of a js component in a python backend?

im not talking about SSR in the context of SPA

and what I'm saying is SSR is almost always needed/an improvement so it's a weird argument for SPAs

i guess im confused... all the Angular SPAs we build have zero SSR

i'm guessing you don't rely on search engines for traffic then

lol yes thats true

These headers dont read very well together, I almost think you can just drop the 2nd line entirely > Hypermedia: A Good Fit If... > > So, when is hypermedia a good choice for an application and/or feature?

> Many companies have adopted react as their standard library for building web applications should React be capitalized

All you need to do is include the htmx script tag and you'll be able to get it working

<script src="https://unpkg.com/htmx.org@1.8.2"></script>

"To avoid this problem, one strategy is to colocate and next the dependent elements for a given resource within an area in the application." I found the phrasing confusing, even though I can get the meaning of it.

obviously , I'm a non-native English speaker/reader/writer

> colocate and next the dependent elements there are definitely some words missing

The article looks good, but obv needs a typo pass. It reminded me of two things: Fielding's description reminded me of the story of shipping containers: a rectangular box revolutionized shipping not because it was efficient, but because it was standard. I think I heard this story in "How to Take Smart Notes" Second is an article I'm blanking on the author about making volatile storage in the web using ping. Basically by just pinging data over the web you can store data in the wires. The data isn't stored anywhere but in the transmissions. I wish I could remember the source. But it just clicked for me that you could have a truly stateless server and still make a bomb UI with htmx, the state only passed in requests and responses

this could be rewritten as "a particular __server__ technology" to avoid this conversation being repeated a million times

One thing I'd like to see mentioned (maybe in the section about games): It's easier to embed SPA components inside hypertext than the other way around.

> It is possible to use Web Workers to handle offline requests, s/Web/Service

Yes I did. But i cannot realize how can I add the other seleciont group of items (e.g. toyota..and bmw. I meant how must I declare them ? ) ..

holy smokes, great insight, there are at least two essays in there

thank you, I have integrated your and @green-activity-6102 's feedback, and also tried to format the "If" subsections better to call them out.

I think it’s s/next/nest “…one strategy is to colocate and next nest the dependent elements…”

"The network is the database." I have used this concept in a past project.