On Tue, Feb 2, 2016 at 2:05 AM, Mikera <mike.r.anderson...@gmail.com> wrote:
> I share the same unease. I haven't quite fully been able to articulate all > the reasons, but here are the things that concern me most: > > 1) Completing the API for data access with the representation > 2) Refactoring challenges > 3) Performance > > These are legitimate concerns. The "Clojure way" has a lot of very nice properties, but you have articulated very well the challenges that come from working with deeply nested, non-encapsulated data. -- 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.
