On Fri, Feb 22, 2013 at 7:47 PM, Korny Sietsma <ko...@sietsma.com> wrote:
> Isn't that always the way, though? Build your program in a powerful, > expressive language, then profile it, find the critical parts, and optimise > them - where possible in the same language, and where that's too > ugly/painful, drop down a layer to a lower level language. > > I'd be curious to hear some opinions on this from the Scala community. I have only been limited by Clojure's performance on one particular program where it was truly necessary to drop down to Java, for the most part performance has been good enough that it has been a non-issue for me. But for those who regularly need to write high-performance code, isn't that supposed to be Scala's sweet spot? The promise of Scala is that it allows you to do a reasonable amount of high-level functional coding while also making it convenient to write mutable, Java-like performance code using the same language with the same semantics. If there are any members of this list who straddle the two worlds of Clojure and Scala, I'd be interested in knowing whether Scala delivers on that promise of being able to write both high-level and performant low-level code, and how much of a difference this makes in practice versus Clojure's approach of expecting the programmer to "drop down" to Java for the best performance. -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
