On Thu, Mar 31, 2016 at 1:02 PM, Timothy Baldridge <tbaldri...@gmail.com> wrote:
> >> I understand, but this library is all about state because it is about > modelling long-lived entities over time as an unpredictable stream of > events act on the model. > > No reason why that can't be handled as a graph of nodes + a single atom. > That's how you would model this in something like Loom ( > https://github.com/aysylu/loom), and how I model all my dataflow graphs. > Start creating recursive self-referencing data structures you're in for a > world of hurt. > <g> I think a part of me is game for seeing if I can support concurrent updates to a cell-based universe, eg, have all eleven players update in parallel, with Clojure STM resolving conflicting updates. But thanks for the suggestion -- I have seen more than one reference to "everything in a single atom". I have to say, porting a hairy library like this is a great way to get up to speed on a new language. Jellz may not go anywhere, but methinks I'll be comfortable with Clojure by the time I am done. Thanks for the input. Cheers, Kenneth -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
