My startup using htmx was there - and it was acquired successfully.

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.

Kinda wild that there is an entire generation of web devs for whom server side rendering is actually the new, strange thing.

Ssr is really about React. Rendering referring to HTML generation using react.

Probably the old school thing is "serving a page"

convenient. I would have liked taking a look at your apps built only using htmx

> the bless of MVC apps.

haha, good one

| They migrated pretty quick to react

One advantage of htmx (along with web components and standard html+css) is that migrating to anything else is much easier than the other way around. A rewrite from an htmx app to a React app can be trivial. A rewrite from React to anything else will not be.

The difference between a 20k MRR startup and lower will almost certainly not be because of HMTX.

this is true in theory but not in practice. just read the article, they came up to the same conclusion. if you want to offer a slick UX (a key element to convince users to pay these days) htmx won't cut it.

Fast is underrated these days and the experience of a fast site TTFB, FCP etc then being more bare metal and eschewing frameworks is wise. Ditching NextJS for Django allowed me to heavily speed up a site. You can do tricks to get React to be fast but that is more work.

Fast impresses people. Too many sites are janky and slow.