I humbly propose that folks shouldn't complain about Clojure being slow for their apps until they have at least one of the following:
1. A targeted benchmark for an important bottleneck in their application, implemented in both Clojure and the current implementation language, with performance results; or 2. A performance model based on an understanding of the Clojure and HotSpot compilation processes, that highlights which particular features of the latter would make their application slower than in its current implementation language. This is not out of elitism but out of an earnest desire to be helpful; it's hard to give good advice on language choice and code optimization when we don't know what the bottlenecks are. Also it's really hard for anyone to optimize their own code unless they themselves know where the bottlenecks are. The latter means that #1 above is surprisingly easy; it often can be done with a simple function trace of a typical run. mfh --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
