4 ms·
Not sure i really get it. So we used to have react/vue/whatever. You click button, and the front end computes the new DOM. No server needed. Then, we decide t
by Gunax 4y ago
Not sure i really get it.
So we used to have react/vue/whatever. You click button, and the front end computes the new DOM. No server needed.
Then, we decide to use htmx, where the server actually computes the new DOM elements, and the client is just a dumb client that displays whatever the server gives.
And now, we give the users browser all of the information to act like a server, intercept the call, and compute what the server would have responded with (saving since network packets and lag).
Did I understand that correctly?
And yea, I also saw that talk about HTMX on HN yesterday... didn't really understand the advantage then either.
- dezmou 4y agoI had the same reaction, maybe this new method of updating the front is more "accessibility friendly"
- dragonelite 4y agoMan in my 8 years of development I have seen the transition away from server side to SPA, from SPA back to server side. Now people are doing server side in the browser. This industry will never become boring if we keep continuing those cycles.
- nymanjon 4y agoCreating MPAs with HTMX is simpler than the SPA approach and makes it so you don't need a "monolith" on the front end. For personal offline first web apps I build I do it this way, except with JS: https://news.ycombinator.com/item?id=33319875 https://news.ycombinator.com/item?id=33319875