On Friday, December 27, 2013 10:02:46 AM UTC-6, Massimiliano Tomassoli wrote: > > I've seen Clojure in action and I know it's extremely concise and > expressive. What I wanted to know is how it copes with complexity when you > develop complex systems. >
My intuition is that getting rid of or reducing mutable state by itself reduces some of the problems of complexity. I'm not against mutability--some things are a lot easier with it--but it's also one of the motivations for modularizing code. One of the purposes of OO is to reduce and constrain dependence on state elsewhere. This is not a full answer because there's still a need for making code modular even with immutability, and because although I've programmed in an FP spirit for a long time, it's only recently, when I started learning Clojure, that I've tried to be more pure about FP. So others will have more insight into what I suggest above. -- -- 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/groups/opt_out.
