Actually, Racket does have serializable closures. https://docs.racket-lang.org/web-server-internal/closure.html https://docs.racket-lang.org/web-server-interna

Actually, Racket does have serializable closures. https://docs.racket-lang.org/web-server-internal/closure.html https://docs.racket-lang.org/web-server-internal/closure.htm... I prefer to explicitly serialize state, because its easier to reason about. Its harder to assert that request A was definitely using/not-using some bit of state that request B was using when you are automatically serializing a bunch of lexical variables in the background. This is just the bias of my personal experience though, I'm a pretty low-level guy.