Based on the recent survey "What are people using Clojure for?", people are mostly using it for non-CPU-intensive work, like parsing, report generation, GUIs, "glue" code.
It's been argued by some that Clojure is as fast as Java, because at worst, you can implement your bottlenecks in Java. I have a problem with this argument, because the data structures that your Java has to work with are still (wasteful) Clojure ones. For example, a matrix data structure in Clojure could be based on Seqs (or Seqs of Seqs) of dynamically typed elements. There is overhead associated with this dynamic typing and mutation of the elements. When you discover that some procedure working on such data structure is slow, you can reimplement it in Java, but do you think it could compete with Java working on native statically typed arrays of floats? I would be curious to know if anyone is using Clojure for CPU- intensive work where performance really counts. I get the impression that Jon Harrop is gearing up to write Clojure for Scientists. Also I remember someone saying they are working on the Shootout entry for Clojure. Has this happened? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
