Ambrose and Meikel, Those are excellent points, but IMO to really be a great clojure developer you really can't get away with not having read the classic goodness that is core.clj. :) And after that having read through the Java code at the core of Clojure: the interfaces and the reader etc.
On Wed, May 9, 2012 at 2:18 AM, Meikel Brandmeyer (kotarak) <m...@kotka.de>wrote: > Hi, > > Am Mittwoch, 9. Mai 2012 08:08:10 UTC+2 schrieb Alex Baranosky: > >> >> 3) read through core.clj, like a fine classic novel. You'll get all >> sorts of good stuff through this process. I can't express deeply enough >> how important this is. Just DO IT. >> >> > I throw in a warning here. core.clj contains quite some code which is > *not* idiomatic Clojure. In particular in the beginning, because the usual > tools are not in place, yet (eg. destructuring). In other cases there are > trade-offs made for performance reasons. So, yes, it is interesting (not > really important, though) to read through core.clj, but you'll need already > a bit of experience with Clojure in order to identify the mentioned issues. > > Kind regards > Meikel > > -- > 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 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
