Comments by "" (@retagainez) on "Creator of HTMX Talks HTMX" video.

  1. 46:42 Locality of Behavior sounds like it is pretty different from separation of concerns, but I do not think they're totally exclusive. They're overlapping slightly in that both of these acronyms are ideas about organizing code. For example, you could group the markup, the scripting, and the styling for a button into one file (demonstrating a locality of behavior), this composes all the code involved in a single button while still providing a separation of concerns by keeping the different syntaxes together but separate from the code/style/markup of other elements in a different file. The developer may pick and choose over the other based on how they've grouped other portions of the code as well, but a consistency in choosing one over the other, or both together is important.
    1
  2. So HTMX simply extends the abstraction of what an anchor, a button and a form can do and generalizing it to other elements through HTMX attributes? It seems like a unique way to extend the declarative nature of HTML and really supports the original idea of HTML. I'm unsurprised that such a useful abstraction hasn't been done until now, I'm more surprised at some of the neat functionality that presents itself just from this concept (the lazy loading, active search, etc.)
    1