Htmx 1.9.0 has been released
&gt; Unfortunately for HTML, CSS transitions are only available if you use JavaScript: you have to change elements dynamically in order to trigger the transitions, which “vanilla” HTML can’t do. In practice, this meant that only the cool kids using JavaScript to build SPAs got to use these tools, further cementing the aesthetic superiority of SPAs.<p>I&#x27;m sorry if my question is not sufficiently informed, but how does HTMX not &quot;use JavaScript&quot; to trigger animations?<p>Have followed the library and approach for a while and tend to compare it to Alpine, which I find a bit more intuitive.<p>But that&#x27;s probably exactly because Alpine isn&#x27;t shy about the fact that you&#x27;re writing JS in the end.<p>I found such solutions (Alpine) a grrat joy to start working with (e.g. a complex form with nested fields, custom autocomplete...) and a nightmare to extend or generalize.<p>The Chrome transition API is very interesting. Also, there certainly is a place for controlling JS via HTML.<p>But for the risk of sounding inpolite:<p>Having read a couple of posts by htmx team, the &quot;htmx is hypermedia, SPAs were invented because X and are a crutch&quot; style intro starts to feel a little repetitive and dated to me. Every post starts with a bashing of &quot;SPAs&quot;, it gets tiresome very quick. SPAs can be simple, they can be complex nightmares.<p>So can HTML-centric &quot;sprinkles of JS&quot; that outgrow their purpose.<p>Also, who are these &quot;cool kids writing SPAs&quot;? It&#x27;s 2023 and it&#x27;s irrelevant if you generate your HTML in PHP, JS, Rust or Python: you need abstraction and modularization for large frontends.<p>That&#x27;s the problem React solves, not just fluffy page transitions.