✳flâneur — a map of the web's best reading

htmx ~ Why Gumroad Didn't Choose htmx

htmx.org · 1,107 words · saved by 1 readers

At Gumroad, we recently embarked on a new project called Helper. As the CEO, I was initially quite optimistic about using htmx for this project, even though some team members were less enthusiastic. My optimism stemmed from previous experiences with React, which often felt like overkill for our needs. I thought htmx could be a good solution to keep our front-end super light. In fact, I shared this sentiment with our team in Slack: “https://htmx.org/ may be a way of adding simple interactions to start” And initially, it seemed promising! As one of our engineers at Gumroad eloquently put it: “HTMX is (officially) a meme to make fun of how overly complicated the JS landscape has gotten - much like tailwind is just a different syntax for inline CSS, HTMX is a different syntax for inline JS.” However, unlike Tailwind, which has found its place in our toolkit, htmx didn’t scale for our purposes and didn’t lead to the best user experience for our customers–at least for our use case. Here’s wh

</> htmx ~ Why Gumroad Didn't Choose htmx Why Gumroad Didn't Choose htmx Sahil Lavingia September 30, 2024 At Gumroad, we recently embarked on a new project called Helper . As the CEO, I was initially quite optimistic about using htmx for this project, even though some team members were less enthusiastic. My optimism stemmed from previous experiences with React, which often felt like overkill for our needs. I thought htmx could be a good solution to keep our front-end super light. Source with htmx - Click Image To View In fact, I shared this sentiment with our team in Slack: “https://htmx.org/

Explore this link on the map →

related reading