Hacker News new | past | comments | ask | show | jobs | submit login

SPAs suck at client side state, they barely work with the back button or scroll bar and if they do its because its reimplemented in JS.



Not browser state, but application state. Lot more boilerplate and glue to do that on server side and ferry it back and forth.


But the application is embedded in a browser. Are you saying it's fine to bin all that UI state the moment the user performs a totally normal interaction with their browser? Accidentally hitting back or refresh in a complex SPA and losing the state of the application is one of the most frustrating experiences on the web, right behind trying to hit back or refresh intentionally and being blocked because the SPA overrides those functions.


No? I simply clarified which state op was referring to. The state of the browser is separate to what's being discussed. SPA's can be good at some state and not others.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: