Actually, even "real" programmers can live for a long time with those training wheels I was talking about. As the Python guys have been proclaiming for 20+ years, performance isn't as important as we think for many (most?) applications. What the Python crowd does, when they're code is slower than required, is to profile their code and maybe rewrite their bottlenecks in C or some other optimization.
By the time a Clojure beginner is doing the kind of hardcore concurrent applications that Clojure is great at, he/she will know how to use a profiler. At the point, they'll be ready (and motivated!) to learn about the nuances of conj and friends. I'm open to corrections and ideas. cs > -- 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.
