Tim Watson

@graninas - thank you! That definitely is helpful background stuff. Yes I'm very interested in performanve metrics too, though they are undeniably hard to nail down. As well as network...

> Note that sending must have the same strictness properties when sending locally as when sending remotely Naive question, but can we not fake that somehow without forcing serialization? It...

> Serializing most (but not necessarily all) data structures will force them to be fully evaluated Of course. Sorry, that's my ML addled brain not fully thinking in terms of...

> In serious applications it is important to control when data structures get forced; it seems rather dangerous to have this depend on network topology. > > I honestly don't...

Oooh - that's cool. I had _no idea_ that was even possible. Don't really know much about existentials yet, so working on CH is turning out to be a bit...

> Yes, but remember that you will need to force that ByteString or still nothing happens :) Cripes yes, I would've forgotten that if you hadn't said something. Cheers! :D

> I don't want to tell you how many subtle laziness bugs I've had to fix in Cloud Haskell so far, or you might lose all confidence in me :)...

Note to self: need to update `postAsMessage` and other auxiliary capabilities in `Node.hs` before merging this.

Hmn, there is some unpleasantness to deal with when implementing this. The channel send operations would also have to be modified in order to maintain the stronger ordering semantics we...

Aren't we still focused on fixing this at the network transport level? I don't think unbounded buffers are sensible, but wait handles and a local thread pool or dedicated thread...