On Aug 10, 4:46 am, Jarkko Oranen <[email protected]> wrote: > I'm not going to start optimising,
Somebody'd better! You always hear this dogma that one should write "elegant" code first and optimize later, and when you do that, a few little changes can make Clojure as fast as Java. Here's your chance to show it :-) > but somehow I doubt that is > the bottleneck The locality of changes is what I doubt. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
