@lispi314@natty also #Prolog, where the program state can effectively be dealt with as "just" a cache of computations that gets refreshed on every program start.
That is ignoring the gnarly bits like external state that no environment has a chance of getting right.
Also #Erlang, the other extreme where you can design for not letting the system go down at all.