Clojure is not good for: - Real time application development, due to the JVM being soft-real time. For example it can't be used for high-performance video pc/ console games, but it could be used for lots of turn-based games. Then again anything done with XNA on the XBOX could be done with Clojure :) (XNA is some form of Compact .NET for the XBOX). - Writing small utility programs, as it requires certain things to be installed properly (For example using "java -serever" with the correct JVM). For example I can't see myself deploying small utility application at work written with Clojure, as it would make people screaming, why they have to install this and that. That won't be the case with big and important application (noone would mind the hidden JVM that I might put along with it).
On Mar 6, 5:15 am, Joshua Fox <joshuat...@gmail.com> wrote: > Is it fair to say that Clojure shines in algorithmic processing, string > processing, concurrency management, but that there are better choices in > other areas: > - "Application" programming , where the key challenge is fitting a standard > three-tier application to the business domain. > - "Enterprise" programming, where the challenge is gluing together > overweight and fragile libraries, and one should always use exactly the set > of software which the API creators envisioned? > > Rich himself has suggested something along these lines, but I wonder what > others think. > > Joshua --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
