Not to discount Rich's work, but all of the ideas in Clojure have been well-known forever, and Haskell and ML implemented these ideas many, many years ago. Clojure lets you use these ideas with some Java libraries; that's its innovation.
Also, I don't really get the whole time analogy, but I can't help but think he wants Comonads, which Clojure does not have. (And due to its type system, will never be able to support well.)
As far as comonads, no - monads and comonads are essentially threaded through a single computation. The reference types I'm talking about are like, and for similar situations as, Haskell's MVars and STM TVars, which wouldn't exist if, e.g., state monads were sufficient.
A common use of MVars:
f x = pure computation
g h m = forever $ hGetChar h >>= putMvar m
do mvar <- newEmptyMVar
forkIO $ liftM f (takeMVar m)
forkIO $ g a mvar
forkIO $ g b mvar
<wait for exit condition>
All we do is read from two handles, concurrently, and eval f for every byte on either handle. The MVar is a natural way of expressing this, but it does lead to potentially undesirable side effects.Writing it in a functional way would probably be better:
f x = pure computation
g h f = forever $ liftM f (hGetChar h)
do forkIO $ g a f
forkIO $ g b f
...
There is now no shared state, since the problem doesn't actually require any. (We could use continuation passing style if we needed to keep state.)Anyway, I am still not sure how Clojure encourages the reference-less style.
Even if you don't think Hickley is on the right track, how can you not like his combination of hands on implementation and search for theoretical soundness?