4 ms·
That makes sense in the context of a window manager, because the processes live outside it, meaning it has very little to no state of its own. But when developi
by sdegutis 11y ago
That makes sense in the context of a window manager, because the processes live outside it, meaning it has very little to no state of its own. But when developing a web app, you have to login to it every time you reload the code, because being signed in is in-memory state.
- damncabbage 11y ago> ... being signed in is in-memory state. Can be in-memory state. Everything beyond toy-sized I've ever worked on has externalised this sort of state to a database of some kind, if only so you can run a second copy for the sake of failover. I don't believe your example is relevant.
- paulddraper 11y agoOr used a signed assertion that is verified with a secret.
- loup-vaillant 11y ago> meaning it has very little to no state of its own That's false. Windows are affected to workspaces. They are sorted in a particular order (set by the user as they move the windows). Each workspace uses a particular layout. One particular window on each workspace last had focus. There's a "current workspace" pointer. That's a bit more than "very little to no state". All of that is preserved upon reload. And I bet my hat all that state was in-memory. Then there is Yi, a text editor. There's no avoiding lots of in-memory state in there. Live code reload in Haskell. It's real.