htmx

“With htmx, there is no frontend state. The html always just reflects the state of the server passively, meaning it cannot go out of sync.”

“Htmx is deliberately maintained as a single, no-dependency file of about 5000loc. The maintainers are of the opinion that it reduces complexity, and I tend to agree.”

“It's exactly because he followed the past two decades of web dev that htmx avoids almost everything about it.”

“Just a few attributes and we get some very reasonable progressively enhanced client/server interactive elements without full page loads.”

“HTMX made things more difficult as it required me to move back to mixing presentation concerns with business-logic and data concerns”

“For me at least, HTMX just makes more sense: you control the flow of content from the client, not from the server as you do with Turbo.”

“Django + Postgres on the backend plus a frontend of HTMX + alpine.js for a light touch of interactivity where needed is a killer combination”

“the main draw of HTMX encourages a completely different app architecture than what the average dev would arrive at with plain JS”

“Its great for forms but that shopping cart example needs code scattered across multiple functions and templates.”

“the impact of recursivedoubts i.e htmx creator on software engineering practices and adhering to simplicity is monumental”

“eventually hit a complexity wall where we were spending more time fighting the tool than solving the business need”

“The criticisms I’m seeing here are all things that are accepted without question in other frameworks but when htmx does it, suddenly it’s too much.”

“Using a tool such as htmx is an effective way for them to solve current challenges while minimizing complexity.”

“The problem I had was that the entire experience became really slow when I had it all working together as one "response"”

“if your backend is already a non-JavaScript server rendered framework like Django then HTMX makes a ton of sense”

“That’s basically a massive hack. Every real world app will need enough js that htmx will require you to put js on front end”

“I find htmx ideal for things that should be static to begin with, and for things that are dynamic, I fail to see how it can handle synchronisation?”

“When we design apps in a way that respects the conventions of REST (hypermedia and resource-oriented design), htmx slots in perfectly.”

“I use htmx for loading and updating resources and I want those operations to work as well as possible even without JavaScript”

“One of the most delightful little swag stunts I've ever seen, and emblematic of the HTMX crew just how much they care about craft and delight in everything they do.”

“Any personal web projects I still use htmx and reached a decent flow with it. Completely simplifies web dev, imo.”

“htmx is extremely easy to integrate with your clojure(script) projects, i found it to be quite pleasant paradigm”

“HTMX really shifts the complexity back to the server in a way that feels more honest and easier to reason about.”

“WebSocket connectivity is one aspect; there is another part of logic and architecture where it falls short.”

“I have just shipped a very useful and interactive app surprisingly quickly for my customer using just htmx with a little Javascript.”

“all the users will be forced to reload the giant JS bundle over and over again, as opposed to just reloading a single resource on a single page like they would with the htmx approach”

“But it seems very narrow cased, there are only so many attributes and their values and you cannot implement anything else.”

“hx-trigger in the response header would handle that cleanly. Fires an event client-side; one global handler shows the error.”

“In HTMX, the logic is spread. What I see is a construct that says "Replace this with the mystery meat from the backend, whatever that is".”

“State management is the key thing - you end up needing to put way more on the backend then you'd otherwise like to.”

“That's the thing that htmx gives you out of the box, along with error handling, progress indicator support, history support, animated transitions”

“You need to track a lot of identifiers for htmx to work properly, and your template and view logic needs to make that make sense.”

“it solves a UX problem that frameworks like Django and Rails suffer from, without needing to bring in something heavy like React”

“The magic of this is that it's pretty easy to make SPA-like webapps with no javascript or complex client side framework.”

“The right (IMO) way to use HTMX is as a replacement for sending JSON over the wire and rendering it into HTML on the client”

“Template Partials and HTMX seems like the Django equivalent of View Components and Stimulus for Rails, which is nice.”

“the htmx developer has made it very clear to me that they are intentionally, ideologically allergic to JSON”

“am I wrong to think that if you use hx-boost to swap in fragments, then the URL that gets updated/saved in history wouldn't actually load the same page”

“I prefer to specify exactly what parts of the page get replaced in much simpler terms, a CSS selector, with `hx-target`.”

“hx-on::after-request response it provides to your callback function does not automatically parse JSON content types”