> > > I've never heard of "imperative model". I'm aware of imperative > programming. Can you expand on what you mean? > > I meant "mutable data model". Sorry for mixing up terms.
> > http://blog.codinghorror.com/separating-programming-sheep-from-non-programming-goats/ > > Hope this helps clarify. > It does. I absolutely agree and get the point that "persistent data structure + multiple cores/threads" approach does solve much here, in fact probably makes things worse. And indeed it is better to queue "Updates from multiple threads" and get it handled by "the mutator thread". But at the same time I hate to have my imagination be "limited" by the hardware designs. That really hurts :-). Best regards, Andy -- 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.
