3 ms·
Basically it boils down to storing state per client. Would you rest the bulk part of it on the server, or on the client? In the initial days of the web, it was
by habibur 5y ago
Basically it boils down to storing state per client. Would you rest the bulk part of it on the server, or on the client?
In the initial days of the web, it was stored on server. But before that, in desktop application era it was stored on client.
- h0l0cube 5y agoIf the state is coming from the server-side database, and has to be persisted there, you'll still need to fetch it, and save it. If there's some transient state that belongs to the web page, vanilla JS is just as capable as a SPA at managing that - and it's just as prone to losing unsaved changes.