Also, repeating this again… the hype and the marketing from HTMX is something I never thought I would see, it’s worse than vercel’s
consider the following examples:
Bulk Update - https://htmx.org/examples/bulk-update/
Infinite Scroll - https://htmx.org/examples/infinite-scroll/
Active Search - https://htmx.org/examples/active-search/
unless you adopt the tautology that anything you can accomplish with htmx automatically means you didn't need a frontend framework, i think many people would expect that accomplishing UX patterns like this would require a front end framework like react or similar
on the marketing front, i don't know what to say. I try to be funny on twitter, but I've been doing that forever and nobody cared. ThePrimeagen and Fireship Dev started covering htmx in July which was a big bump, and the Github Accelerator helped too. I think i mostly got lucky: right place, right time, right vibe. I don't spend any money on marketing and I don't have any VC or FAANG backing.
the distinction i like between "library" and "framework" is:
* a library you call into
* a framework calls back into code you provide
Using this definition, from a javascript perspective, htmx can be considered a framework, since you are providing "code" (well, html attributes) that it is hooking up event handlers and calling back into.
However, from an HTML perspective, htmx is a library, in that you "call" into the htmx code by "invoking" attributes.
I lean towards calling htmx a library because I have a bias towards the HTML-first interpretation of htmx, but I admit that you could easily justify the other interpretation of htmx.