On Aug 11, 4:35 pm, Chas Emerick <cemer...@snowtide.com> wrote: > Maybe others will disagree, but I don't think that standard can ever > be met. There will always be tasks for which clojure is slower than > java, just as there are tasks where java is slower than assembly. > > I suspect that those cases will become rarer and rarer as progress is > made on all sorts of fronts, but I doubt the objective is to attain > 100% performance parity. I'll bet that order-of-magnitude parity > across some vast majority of use cases is a likely maxima, with many > tasks reaching true parity (and virtually all tasks reaching practical > parity, e.g. any marginal performance difference is negligible w.r.t. > broader objectives).
I agree wholeheartedly. Let's optimize wherever possible, but drop on the side-by-side comparisons. -SS --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
