On Tuesday, November 27, 2012 at 2:17 PM, Cryptic Swarm wrote: > > 2) It seems this would mainly be useful as a teaching tool because I don't > > see how it could work with non-deterministic behavior such as io events. > > > Yes, mainly useful for teaching/learning purposes, but not really because of > io events. Once something happens it, it happened. The data-structures are > immutable. When you go backward what has already happened won't change. > However, when you go forward again you will potentially fork the computation > tree (if going forward has a different side effect than previously). This would still be incredibly useful for understanding what's happened after the fact in complicated closure-based execution scenarios. It feels like it's a pretty short hop from this to some of the stuff people have been doing with monoids / applicative functors / monads / the "semicolon operator" in JavaScript, only with an easier method for metaprogramming.
Perrin, have you put the framework for this up on github yet? I'd totally love to play with it. F -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
