The benefit of Clojure are its built-in data and programming models, which are well-suited for the concise expression of concurrent computations. Since fighting the incidental complexity is, along many others, a very important concern in building concurrent apps, Clojure has an edge there over plain Java---but that's where its advantages stop. All the down-below issues of concurrent performance (and there are many) are shared with Java.
-marko On Sunday, April 28, 2013 4:51:04 AM UTC+2, Cedric Greevey wrote: > > https://en.wikipedia.org/wiki/Intel_MIC > > 50+ cores?! Clojure will leave every other language in the dust on > something like that, thanks to its inherently scaleable concurrency > constructs. Try writing a 50-threaded Java application without getting > deadlocks all over the place, or cheating and using very coarse-grained > locks (have fun with the task manager showing 2% CPU utilization when your > app is running full-bore!). > > If big, 32-bit addressing spaces were what made automatic memory > management really begin to come into its own (and with it, Java), then it's > doubtless 50-core machines that will make automatic concurrency management > really begin to come into its own. > > -- -- 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.
