I don’t think it makes much sense as a HTML standard. HTML is ultimately a document format that is used for more things than just websites. Maybe as a separate extended HTML format that browsers...
I don’t think it makes much sense as a HTML standard. HTML is ultimately a document format that is used for more things than just websites. Maybe as a separate extended HTML format that browsers can implement such that the additional JavaScript required becomes obsolete.
The HTML standard included application-like capabilities from the beginning using the form element and the iframe element. You might be thinking of XML?
The HTML standard included application-like capabilities from the beginning using the form element and the iframe element. You might be thinking of XML?
This was the first time I have heard of it. At first I thought it was a terrible idea because of the removal of separation of concerns. But the more I think about it, it doesn’t seem that bad. It...
This was the first time I have heard of it. At first I thought it was a terrible idea because of the removal of separation of concerns. But the more I think about it, it doesn’t seem that bad. It solves a lot of the HTML cruft about building dynamic pages and it’s probably a better implementation than most solutions that have similar ideas.
IMO, the "separation of concerns" between HTML/CSS/JS through IDs and classes was only useful back when it was created, when splitting the application into components wasn't as popular. Now, when...
IMO, the "separation of concerns" between HTML/CSS/JS through IDs and classes was only useful back when it was created, when splitting the application into components wasn't as popular. Now, when the vast majority of web applications, even static ones, are written with components, it makes much more sense to bundle layout, styling and logic together. This is why people like to use things like Tailwind.
Indeed, the creator of HTMX has written an essay on that, he calls it "locality of concerns": the idea of keeping concerns in the same place so it's easier to reason about a unit (or component) of...
Indeed, the creator of HTMX has written an essay on that, he calls it "locality of concerns": the idea of keeping concerns in the same place so it's easier to reason about a unit (or component) of code . That's why HTMX is nice to use with things like Tailwind and AlpineJS.
Ultimately HTMX is just an extension of existing web ideas. Previously it was link/form -> whole new page, but with a few tweaks it's possible to do link/form/button -> partial new page. Just that...
Ultimately HTMX is just an extension of existing web ideas. Previously it was link/form -> whole new page, but with a few tweaks it's possible to do link/form/button -> partial new page. Just that enables 80% of what SPAs are typically used for.
Not much to say, but HTMX is terrific, and really should be integrated into the HTML standard.
I don’t think it makes much sense as a HTML standard. HTML is ultimately a document format that is used for more things than just websites. Maybe as a separate extended HTML format that browsers can implement such that the additional JavaScript required becomes obsolete.
The HTML standard included application-like capabilities from the beginning using the form element and the iframe element. You might be thinking of XML?
This was the first time I have heard of it. At first I thought it was a terrible idea because of the removal of separation of concerns. But the more I think about it, it doesn’t seem that bad. It solves a lot of the HTML cruft about building dynamic pages and it’s probably a better implementation than most solutions that have similar ideas.
IMO, the "separation of concerns" between HTML/CSS/JS through IDs and classes was only useful back when it was created, when splitting the application into components wasn't as popular. Now, when the vast majority of web applications, even static ones, are written with components, it makes much more sense to bundle layout, styling and logic together. This is why people like to use things like Tailwind.
Indeed, the creator of HTMX has written an essay on that, he calls it "locality of concerns": the idea of keeping concerns in the same place so it's easier to reason about a unit (or component) of code . That's why HTMX is nice to use with things like Tailwind and AlpineJS.
Ultimately HTMX is just an extension of existing web ideas. Previously it was link/form -> whole new page, but with a few tweaks it's possible to do link/form/button -> partial new page. Just that enables 80% of what SPAs are typically used for.
<noise> Aside from the "stop trying to make fetch happen" meme posted in the link, for younger folks, I have nothing meaningful to contribute</noise>