2 ms·
...or people could just learn javascript and stop using any framework. Honestly, intercooler.js aka htmx always seemed to be the worst of both worlds to me: Yo
by xg15 3y ago
...or people could just learn javascript and stop using any framework.
Honestly, intercooler.js aka htmx always seemed to be the worst of both worlds to me: You get back the heaps of redundant, uncacheable HTML fragments from the pre-SPA days, but you also take the dependence on javascript, unpredictable page behaviour and invisible page state from SPAs.
(Example: htmx now has websocket support - that is, as long as each server-to-client message is an html fragment. Have fun writing a basic websocket chat app and echoing back the entire chatlog including UI and formatting every time someone says something)
Why would you want that?
- minaguib 3y agoI'm not a frontend dev, but from cursory reading of htmx docs, it seems your example implying every chat message would require sending the full log to every user is a bit of a stretch - a more natural way would be to transmit only the new messages and use one of the "before" or "after" swap settings to insert them where appropriate.
- xg15 3y agoAh, that seems to be correct. I take that back then.
- traverseda 3y ago>Have fun writing a basic websocket chat app and echoing back the entire chatlog including UI and formatting every time someone says something No, you just append.