HTMX (and similar) solves a lot of this. It so happens that we end up building two apps one frontend and one backend with SPAs as built today. I'd rather build a lot of it on the server side, and add some dumb interactivity on the client (show/hide, collapse/expand, effects). There is still a place for SPA though.

▲

naet 4 days ago | parent [-]

HTMX does the opposite of this, it requires many more round trips to the server instead of using client side JS to do work.

▲

recursivedoubts 4 days ago | parent | next [-]

htmx does not require many more round trips to the server, front end scripting is perfectly compatible with htmx:

https://hypermedia.systems/client-side-scripting/

in addition to native html features like <details>, etc.

htmx can often decrease the number of trips to a server because in the hypermedia model you are encouraged to deliver all the content for a UI in one fell swoop, rather than in a series of chatty JSON requests that may be made due to opaque reactive hooks.

▲

aquariusDue 4 days ago | parent | prev | next [-]

I find Datastar to be a better replacement for HTMX, especially now that it can also do plain requests instead of Server-Sent Events. You also don't need Alpine.js combined with HTMX anymore.

	▲	chuckadams 4 days ago \| parent [-]
		First time I've heard of Datastar. Not sure what to make of it yet, but the video on data-star.dev is certainly one of the cutest things I've seen all year!

▲

princevegeta89 4 days ago | parent | prev | next [-]

Many more round trips to the server is okay - it is the server after all and it is easy to scale it.

▲

goatlover 4 days ago | parent | prev | next [-]

Does it matter how many round trips are made to the server if they're fast enough to be seamless?

▲

throwaway7783 4 days ago | parent | prev [-]

I meant for the SPA-like experience.