I would argue the “more capable” frameworks, while invented with the best of intentions, have become unmanageable, unmaintainable monstrosities that just keep rolling out, as you put it, solutions in search of a problem.
htmx is not meant to do anything fancy that you can’t do with Ember/Angular/React/Vue/etc.
The main motives for me deciding to go with htmx:
- No duplication of data models and routing, and all business logic stays on the server-side where it belongs.
- Locality of behavior: you can see exactly where a request will be triggered and what will be done with the response, so less jumping between files or scrolling up and down.
- No build step, no dependency hell, and no outrageous churn; just include one JS file that browsers should be able to run indefinitely.
htmx is not meant to do anything fancy that you can’t do with Ember/Angular/React/Vue/etc.
The main motives for me deciding to go with htmx:
- No duplication of data models and routing, and all business logic stays on the server-side where it belongs.
- Locality of behavior: you can see exactly where a request will be triggered and what will be done with the response, so less jumping between files or scrolling up and down.
- No build step, no dependency hell, and no outrageous churn; just include one JS file that browsers should be able to run indefinitely.