I'm gonna need more explanation here
Discussion
Which part? Lol
htmx.org
why browsers are the problem? how htmx, a js lib, fixes js? how more markup in my HTML is the answer?
The story of JS has been to move as much of the backend to the frontend. HTMX moves mostly everything to the backend and allows the client to just handle rendering html. I can build an app with half the code base with the same features with more responsiveness and performance. On top of that, I can build quickly. HTMX extends html, as it should have been all along.
You have more markup in your HTML so you can have less dependacy on js and all it's crap in the rest of your project.
the story of js has been to make richer, more interactive websites while minimizing data transfer over the wire at runtime. I agree we've probably gone too far, but htmx is just bringing back memories of jQuery and its hellhole of plugins.
we have had solutions for backend handling everything. it's just HTML templating. htmx does not do what you say. instead of making the frontend focus on user interaction and response to those actions, it delegates fragments of a view to a backend that is also responsible for serving up full pages and potentially serving up data in another format like json. it taken a clean-ish separation of data manipulation and data rendering and instead made it worse. just use full backend templating and go to the backend with every button click at that point. serving up HTML fragments from an API is gross.
in addition, the entire setup is facilitated by a js lib. it's just complicating the logic of what owns the fragments of HTML for rendering data. as a backend developer myself, it's a really gross way of building an application.
but that's just my two sats.
I just found this today. It's a great example and explains why this would be a much better way to build an application in most cases than an overly complex framework.