Less Htmx Is More

> In my opinion, most websites should be using htmx

In my opinion, in five years no one uses htmx, but another shiny toy. Hence, how about not starting to use it at all?

This applies to every single web framework/library, so I guess your point is that nobody should start making web things?

I don't share the opinion you've quoted there, but neither do I share yours. Hmtx isn't actually a shiny new toy, it's just a rebrand of intercoolerjs - and I found out about that one in 2014.

That makes the time since it's inception to date longer then the time between initial react release and initial intercoolerjs release

Hi, author here. The full quote is: "In my opinion, most websites should be using htmx for either:", and then I list two cases where I think htmx is appropriate.

In context, it's clear that I'm not saying "everyone should use htmx," but rather "if you are using htmx, here is how I recommend you do it."

As for the shiny object concern, I have a talk (which you can also find on this blog) called "Building the Hundred-Year Web Service", that dives into that question.

It kind of is - although, with a twist.

I think most things done currently with the frontend "frameworks", could be achieved with standard HTML5+JS, without any "build steps" or other bloat involved.

This said, there is a case for building on a commonly used mature platform, such as React, to speed up the development cycle and in order not inventing the wheel again.

Nobody gets fired for buying IBM, I guess :(