On Aug 11, 2009, at 4:26 PM, fft1976 wrote:
> I've seen that. There is a difference between "I can come up with two > snippets in Java and Clojure doing the same thing at the same speed" > and "For any Java code, I can write Clojure code that does exactly the > same thing just as fast". The difference is in quantification: > universal vs existential. http://en.wikipedia.org/wiki/Quantification#Logic 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). - Chas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
