<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ysavir</author><text>This is the thing that makes me lose interest in HTMX. People talk about it like it eliminates the need for JS&amp;#x2F;React&amp;#x2F;etc, but as far as I can tell, you&amp;#x27;re still writing those same templates, just using your backend language instead of JS. Which is convenient, but hardly &amp;quot;less code&amp;quot;, just a different language, and that backend language probably lacks a lot of functionality you&amp;#x27;d want for UI convenience. That&amp;#x27;s all fine if you&amp;#x27;ll never want those UI conveniences, by my experience has been that the want of those UI conveniences creep in over time, and eventually you regret not using something that makes them native and easy.&lt;p&gt;I haven&amp;#x27;t actually played around with HTMX, so I might be sizing it up wrong, but it&amp;#x27;s mission statement just never resonated with me enough to want to try it out.</text><parent_chain><item><author>rtpg</author><text>One thing I&amp;#x27;ve been struggling with using HTMX... with an app and a frontend REST API I&amp;#x27;ve found I can really kinda quickly craft a frontend by filtering down whatever resources I need (though it&amp;#x27;s honestly pretty wasteful at times).&lt;p&gt;With HTMX I&amp;#x27;m finding myself needing to have as many backend views as I have ways of interacting with a page. I still have to write the frontend, and on top of that I gotta make a bunch of one-off backend views for many interactions. What am I doing wrong?</text></item><item><author>simonbarker87</author><text>I’ve been using htmx for over a year now for our internal management application (order monitoring, partner management, CAD model uploading and management type stuff) and I continue to be delighted at how quickly I can add features and iterate existing ones. I write way less client side JS, the app is very fast and responsive and I don’t have to write the app twice like with a SPA + API.</text></item></parent_chain></comment><story><title>Htmx, Raku and Pico CSS</title><url>https://rakujourney.wordpress.com/2024/09/08/htmx-raku-and-pico-css/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>djbusby</author><text>I make htmx sites built around view fragments rather than pages. And when I need a page it&amp;#x27;s just a set of fragments. I make &amp;quot;API&amp;quot; endpoints fir the needed fragments and call via ssr on first paint, then as needed from the htmx side.</text><parent_chain><item><author>rtpg</author><text>One thing I&amp;#x27;ve been struggling with using HTMX... with an app and a frontend REST API I&amp;#x27;ve found I can really kinda quickly craft a frontend by filtering down whatever resources I need (though it&amp;#x27;s honestly pretty wasteful at times).&lt;p&gt;With HTMX I&amp;#x27;m finding myself needing to have as many backend views as I have ways of interacting with a page. I still have to write the frontend, and on top of that I gotta make a bunch of one-off backend views for many interactions. What am I doing wrong?</text></item><item><author>simonbarker87</author><text>I’ve been using htmx for over a year now for our internal management application (order monitoring, partner management, CAD model uploading and management type stuff) and I continue to be delighted at how quickly I can add features and iterate existing ones. I write way less client side JS, the app is very fast and responsive and I don’t have to write the app twice like with a SPA + API.</text></item></parent_chain></comment><story><title>Htmx, Raku and Pico CSS</title><url>https://rakujourney.wordpress.com/2024/09/08/htmx-raku-and-pico-css/</url></story>