Hello, 2009/12/17 Dmitry Kakurin <dmitry.kaku...@gmail.com>
> Judging by the article you've spent very little time "learning" > Clojure and have managed to get every key point wrong: > > > Clojure is a multi-paradigm language > > no it's not, and it's most certainty not an OOP language: > http://clojure.org/rationale > > > Functional programming finds its best implementation in the homoiconic > language family. > > very debatable statement > > > The attitude of the language [...] is to be a better Java > > Clojure's attitude is to be a great language for JVM platform (and > maybe CLR) _other_ than Java. With different set of goals. Granted > it's often _compared_ with Java for obvious reasons. > > > one will not appreciate Clojure for being a better LISP. Instead Clojure > tries to be a better Java with LISP syntax. > > Not sure who the 'one' is. I for one do appreciate Clojure as a better > Lisp :-). > > > Owing to the above attitude, many of the language constructs exist so > that one can do what Java cannot do > > Is Java some kind of "golden standard" in language design now? > > > For e.g. tail calls cannot be optimized in the Java > > Correction: in current version of JVM > As for tail calls, Clojure has to live with limitations of the target > platform. > > > In Clojure this identity is lost, because practical implementation > difficulties are put ahead of clean design. > > IMHO Clojure has a rather strong and unique identity. Here is my > elevator pitch for Clojure (not any kind of analysis, just what makes > Clojure attractive to ME): > - Lisp dialect designed for JVM with transparent interop > - Better Lisp than Lisp :-) Simpler/cleaner than Common Lisp, more > practical than Scheme. > - Rich immutable collections unified by a concept of sequence > I just learned (the hard way, by being humble and asking :-) ) on #clojure that one does not say "immutable" collections but "persistent" collections, since "persistent" conveys a lot more information about what Rich has achieved than just saying "immutable". :-p > - Unique and intriguing approach to state, identity and concurrency > - Very dedicated and talented author, great community > > In general I'd like to second Luc's "be humble" comment. And do your > home work before doing "analysis". > > - Dmitry > > On Dec 11, 1:04 pm, kusi <kusim...@gmail.com> wrote: > > http://kusimari.blogspot.com/2009/12/analysing-clojure-programming-la... > > -- > 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<clojure%2bunsubscr...@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
