My comment from the other thread: The CEO of gumroad mentioned on twitter that he had tried out htmx for a project but decided to go with NextJS instead. I asked him if he was willing to write up his experience and he graciously agreed to do so. I have been looking for a thoughtful negative experience with htmx to host on the htmx website and I am very thankful he was willing to put in the work to produce one.
Why Gumroad Didn't Choose Htmx
21–30 of 216 posts
Re: Why Gumroad Didn't Choose Htmx
#22This reeks of ad-hoc vibe-driven development.
Re: Why Gumroad Didn't Choose Htmx
#23This 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
#24This 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
#25Re: Why Gumroad Didn't Choose Htmx
#26I literally only ever hear about htmx from YC. I still don't know what the point of it is, it seems like one of those opinionated programmer things like "I don't use a framework" or "you don't need javascript to make my site work"
Re: Why Gumroad Didn't Choose Htmx
#27I will start using htmx as soon as there is a 20K MRR startup built only with it.
They migrated pretty quick to react after the acquisition due to team dynamics (offshore big teams - seeped into JS heavy client, thin server culture). htmx was a struggle there as well.
It worked amazing for us as a small team where everyone was full stack and I always build using htmx-first now. But, it is a struggle for folks who have been working in React-like patterns for 5+ years and never experienced the bless of MVC apps.
Re: Why Gumroad Didn't Choose Htmx
#28I used it recently to build a small crud admin page and I soon reached the limits of the technology; in the ends I rewrote it in solid.js - because next.js / react are pretty slow and employ the wrong abstractions.
I think htmx for static + solid.js for interactive is a great combination - albeit I dream of a framework which will excel at both.
Re: Why Gumroad Didn't Choose Htmx
#29> AI and Tooling Support: It’s worth noting that AI tools are intimately familiar with Next.js and not so much with htmx This is stated as a very matter-of-fact downside, but this is a pretty crazy portent for the future of dev tools / libraries / frameworks / languages. Predictions: - LLMs will further amplify the existing winner-take-all, first-mover nature of dev tools - LLMs will encourage usage of open-source to…
Re: Why Gumroad Didn't Choose Htmx
#30My comment from the other thread: The CEO of gumroad mentioned on twitter that he had tried out htmx for a project but decided to go with NextJS instead. I asked him if he was willing to write up his experience and he graciously agreed to do so. I have been looking for a thoughtful negative experience with htmx to host on the htmx website and I am very thankful he was willing to put in the work to produce one.
I'm curious in particular about the call out around drag-and-drop. Is that something you agree with? Is drag and drop difficult with htmx and if so, is that something you plan on tackling?