On Mon, May 9, 2011 at 6:43 PM, Mike Meyer <m...@mired.org> wrote: > One thing that happens to such posts is they turn into threads of > "best way to solve this problem" - where "best" varies by author.
I'm not sure if you intended this as a criticism of the idea, or if you are thinking the same thing I am, but I'd like to point out that that can be a good thing. The varied approaches may be more instructive than just one, particularly when optimized with different criteria, and tradeoffs may end up illustrated among things like speed, memory use, clarity/style of the code, avoidance of mutation/threadsafety, and other considerations. As long as things don't get out of hand with arguments about the "one true way" (if necessary, moderate the forum to squelch such tangents), such alternative points of view should be encouraged. Of course, for Clojure code specifically we already get a fair amount of traffic in this list that fits this pattern -- though it is mixed in with other traffic, from announcements of new library versions to debates on the design of Clojure itself to questions about getting emacs/vimclojure/counterclockwise up and running and more. -- 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
