Sorry, I don't believe it. I believe with <arbitrary, unspecified, framework-external work & attention to detail> you could progressively degrade an HTMX page, but there's nothing free about it.
Consider this example linked in the thread somewhere, and argue convincingly it would be useful for someone with JS disabled. Otherwise, argue for me why the examples aren't canonical, and that the machinery to wire this meaningfully wrt progressive degradation would be trivial. https://htmx.org/examples/active-search/
You seem to have a very strong negative opinion about something which you have a very tenuous understanding. Is this you approach most things you don't understand?
> Is this you approach most things you don't understand?
I would be delighted if you could do two things for me. One, can you explain what it is I seem to be misunderstanding?
Two, could you answer the question - already posed - which would backup your claims that <noscript> is a benefit HTMX for free:
> Consider this example linked in the thread somewhere, and argue convincingly it would be useful for someone with JS disabled. Otherwise, argue for me why the examples aren't canonical, and that the machinery to wire this meaningfully wrt progressive degradation would be trivial. https://htmx.org/examples/active-search/
It's a shady marketing technique to hijack that term when it doesn't work that way.