What is HTMX?
React or Angular helped people do whats called "Single Page apps", a single page is loaded first and then for everything user does we only updates relevant parts of the page, fetching only neccessary things from the server. The disadvantage here is that maintainance of the code for both client and server gets complex and also the browser is over burdened.
Bad SPAs give terrible experience to user and their code is very hard to follow. Also SPA tech does not work well with old frameworks like Django, Rails and PHP frameworks which were primarily designed for MPAs.
Something like HTMX is likely to help DJango, Rails and Laravel like frameworks to build more rich applications that behave like SPAs but with MPA like approach.
Unlike other framework HTMX is a very simple library which does not require any build process. It executes in the browser. No additional compilation like React code is required.
It is extremely easy to write ajax and websockets code with HTMX and these are supported as primary citizens.
In above example /graph is being fetched but while the loading is in progress the img is being displayed. The trigger attribute tells the library to update the markup only after /graph is fully loaded. See it in action.
In above code when you click on the button, the get path is fetched and the content of this request is than added to the item with selector replaceMe.
You can see more examples of HTMX in action here.
You can learn basics of HTMX over one evening. Since simplicity is its goal, learning it is also ridiculously simple. HTMX also can be used along with your other front end technologies such as react to vue. It especially plays well with fullstack frameworks like Ruby on Rails and Django which prefer to render html on the server.
I will not be surprised if HTMX does get widepread adoption for smaller and simpler web applications. In fact as it becomes more successful we can rely on React and Vue eco system to adopt some of its elements into their own frameworks.