3 ms·
Regular server/client beats SPA because each request starts with an empty state, whereas SPAs build up bugs as they try and fail for mutate state over time. Wh
by gorgoiler 5y ago
Regular server/client beats SPA because each request starts with an empty state, whereas SPAs build up bugs as they try and fail for mutate state over time.
What about an SPA that made internal requests to a server backend, running in the browser?
- nawgz 5y ago> each request starts with an empty state Strange place to post such a … misguided stance. HTMX regularly brags about how it’s meant to be used to mutate the DOM the user already has loaded, thru custom HTML attributes handled by their JS framework. You’re just arguing in favor of HTML, but HTMX is trying to have their cake and eat it too. JS-level state is clearly easier to manage than DOM-level.
- recursivedoubts 5y agoWell, using Hypermedia As The Engine of Application State doesn't seem too... outside the lines of the web.
- nawgz 5y agoYes, a giant tree representing a view layer which blends data with presentation is clearly the canonical representation of app state...
- recursivedoubts 5y agoWell, according to Roy Fielding...