<story><title>Htmx and Web Components: A Perfect Match</title><url>https://binaryigor.com/htmx-and-web-components-a-perfect-match.html</url></story><parent_chain><item><author>Kiro</author><text>Is anyone using htmx in a large project? Seems like it could be great for small things, but unmaintainable at scale, and that all the praise is based on the former.&lt;p&gt;Something tells me that the backlash will be enormous.</text></item></parent_chain><comment><author>davedx</author><text>I doubt it. I think it&amp;#x27;s like svelte, but a bit earlier in the hype cycle.&lt;p&gt;The &amp;quot;State of JavaScript&amp;quot; survey is illuminating for these kinds of technologies. They often follow a trajectory towards &amp;quot;more liked&amp;quot;, while remaining consistently and firmly in the &amp;quot;not used&amp;quot; quadrant. Everyone thinks they look amazing and refreshing, and maybe some people have even actually written some small apps in them, but (almost) nobody is using them at scale.&lt;p&gt;It&amp;#x27;s not a bad thing really, but the hype can be annoying</text></comment>
<story><title>Htmx and Web Components: A Perfect Match</title><url>https://binaryigor.com/htmx-and-web-components-a-perfect-match.html</url></story><parent_chain><item><author>Kiro</author><text>Is anyone using htmx in a large project? Seems like it could be great for small things, but unmaintainable at scale, and that all the praise is based on the former.&lt;p&gt;Something tells me that the backlash will be enormous.</text></item></parent_chain><comment><author>sli</author><text>In theory it seems like it should scale like a variation on a pretty standard full stack application that does the HTML work on the backend -- as opposed to a SPA -- but instead sends fragments instead of entire pages. I&amp;#x27;m also be curious to see how it plays out in practice, since it&amp;#x27;s been pretty neat for my small projects and I&amp;#x27;m intrigued by it, generally.</text></comment>