3 ms·
> managing state on the server is not fun at all. Really? I've never found that difficult. Sessions exist, URL parameters exist... Perhaps in a complex SPA you
by xp84 1mo ago
> managing state on the server is not fun at all.
Really? I've never found that difficult. Sessions exist, URL parameters exist... Perhaps in a complex SPA you can have trouble, but so many of the "applications" I've worked on are just glorified documents.
- mexicocitinluez 1mo agoI haven't used sessions in over a decade and haven't regretted that decision once. It opens up a whole new class of problems you don't have when using client-side frameworks.
- yawaramin 1mo agoSo what do you use instead?
- mexicocitinluez 1mo agoIt depends on the specific data. Do you have anything that you store in session in mind? Having the client/server split has made this a lot easier to reason about. I store client state on the client and server state stays on the server.
- yawaramin 1mo agoI’m talking about auth, like a session cookie. What do you use for auth?
- mexicocitinluez 1mo agoI use Entra, so the session cookies are created through login.microsoft.com. Which means I'm not actually managing the session. When I said I don't use sessions, I should have specified I don't use them for application state (or roles and stuff).