Why Gumroad Didn't Choose Htmx
htmx.org
Why Gumroad Didn't Choose Htmx
1–10 of 216 posts
Re: Why Gumroad Didn't Choose Htmx
#2> For instance, implementing a drag-and-drop interface for our workflow builder proved to be a significant challenge with htmx, requiring workarounds that felt clunky compared to the smooth experience we could achieve with React libraries.
HTMX is better if you have a frontend bundle that does just enough but no more. Hook into the htmx.onLoad event and then look for markup with attributes in the content being loaded (for example, columns, cards, tasks, etc) to attach to. You can then, for example, bind sortable.js onto the rendered markup, and then wire sortable events to state updates via HTMX. Really pretty straightforward. They even have an example of exactly this in the docs: https://htmx.org/docs/#3rd-party
Re: Why Gumroad Didn't Choose Htmx
#3This is a wonderful advertisement for the things that HTMX is good for and the thing it isn't.
It's obviously tongue-and-cheek but I think it makes the case well!
Re: Why Gumroad Didn't Choose Htmx
#4Kudos to htmx.org for hosting this essay.
Re: Why Gumroad Didn't Choose Htmx
#5Kudos to htmx.org for hosting this essay.
I really do value services/tools that explain why you shouldn't use it, as well as why you should.
Re: Why Gumroad Didn't Choose Htmx
#6Kudos to htmx.org for hosting this essay.
It's really humble and honest of them to put something like this up but in the end at least they have something to point to now if people pick it up and get mad that it doesn't meet their needs
Re: Why Gumroad Didn't Choose Htmx
#7I like how they compare server-side validation with React's client-side (only?) one.
Wasn't able to relate to other puns all that much unfortunately.
Re: Why Gumroad Didn't Choose Htmx
#8Kudos to htmx.org for hosting this essay.
Yeah it's linked from https://htmx.org/essays/ under "On The Other Hand…"
Re: Why Gumroad Didn't Choose Htmx
#9Comparing it with React is a low bar, since a lot of people are unhappy with React.
Arguments like "React is popular, AI knows it", or "React is popular, lots of component have been written in it" seem weak.
A proper antithesis for htmlx should compares it with SPA.