Tailwind, htmx, AlpineJS, etc all seem to suggest we took a wrong turn giving up on XHTML, because as it turned out, we actually did want the ability to refer t

Tailwind, htmx, AlpineJS, etc all seem to suggest we took a wrong turn giving up on XHTML, because as it turned out, we actually did want the ability to refer to declarative attributes for distinct sets of browser behavior: styling with no real expectation of handling `@media print` in the case of tailwind (obviously you can but its likely not the dominant use case), IO and composite DOM mutation in the case of htmx and AlpineJS; etc. Moreover, XML namespacing allowed us to scope the web authoring experience, so that one could fluidly scale from the default case of document layout up to whatever desired levels of interactivity and the semantics to support that, all the while engaging with a minimum of JS. Being able to easily integrate new semantics in an opt-in way could've allow for faster innovation.