I'm taking a cognitive processing model approach [with primitives of] data ("facts") and references ("values") and the memory model to handle and relate them takes the primary stage. This would allow for existing languages to take advantage of the temporal memory model (which is content addressable, btw) and also permit a native language with first class support for 'POV' semantics to also use it.
I'm calling this approach to building information systems "Optimistic Realism".
Btw, are you familiar with David Barbour's Reactive Demand Programming and if so, what are your thoughts on it?
Glitch is an approximation to Backus's "Applicative State Transition Systems". see:Backus:"Can programming be liberated from the von Neumann style?" www.thocp.net/biographies/papers/backus_turingaward_lecture.pdf
Since 1980, I have applied ASTS in the development of Hard Real Time Avionics Systems Software for Military & Commercial Aircraft and Spacecraft.
I have licensed this code exclusively to Aerospace companies over the years.
It has proven its value in the development of verifiable software.
For reasons that Backus states, the approach is not easy to comprehend nor apply, and requires very specialized tools (data flow debugger & proof system).
The tool is known as "Synthesis" in the Aerospace Industry.
Everybody, really, if you have time and would like a look into the future, read chapter 2 of the paper seanmcdirmid posted (and co-wrote).
There are ways to tame side effects without going monads, which don't really fix the complexity problem anyways (it just makes all effects explicit). See this paper for ideas on how to do that:
http://research.microsoft.com/pubs/211297/managedtime.pdf
We shouldn't treat state like an unwanted but necessary evil, we should embrace it and deal with it.