It is definitely "anti-javascript" or more precisely "anti-SPA". I've read the blog posts.

htmx is pro-JavaScript:

https://m.youtube.com/watch?v=9ZhmnfKD5PE

It is not anti-SPA, but pro-hypermedia for the right problems:

https://htmx.org/essays/when-to-use-hypermedia/

htmx is a front end library of peace

JS != SPA though, no matter how many frontendies want to believe it is equivalent.

It’s funny to equate JS with SPA. We’ve had JS on the web since day 1 to add interactivity to otherwise static pages. SPA only became a thing decades later.

I was there on day 1 of the web and js was not yet even a twinkle in anyone's eye.

?? Since day1?

Day 1505 by my count. Say, does anyone know Javascript's birthday?

There was a pretty long gap between JS being created and people making significant use of it.

Sorry but you must have read with your eyes closed. Here’s a quote from the HTMX website:

”After all, both htmx and hyperscript are built in JavaScript. We couldn’t have created these libraries without JavaScript, which, whatever else one might say, has the great virtue of being there.

And we even go so far as to recommend using JavaScript for front-end scripting needs in a hypermedia-driven application, so long as you script in a hypermedia-friendly way.

Further, we wouldn’t steer someone away from using JavaScript (or TypeScript) on the server side for a hypermedia-driven application, if that language is the best option for your team. As we said earlier, JavaScript now has multiple excellent server-side runtimes and many excellent server-side libraries available.”

https://htmx.org/essays/hypermedia-on-whatever-youd-like/