@brandon Correct, a lot of my language research is about how pure state + update function languages have this idea of durable execution implicit without having to jump through hoops (like temporal) and the benefits that brings. The idea of Elm-like actors communicating with each other persistently as the fundamental process abstraction for an OS is appealing to me.
It seems to me like right now if you want persistence when building an app you are either stuck in "I want it very simple, I'll use a toml/json file somewhere in the file hierarchy and hope for the best" or I embed sqlite and save it somewhere in the file hierarchy.
I'm very interested in atomic storage being part of the OS, making it super easy to store data, persistently and safely with many different small composable programs that you can only access if given that capability.