The risk of breaking changes gets smaller all the time. There is always a small chance that something might need to be changed that would break your code. It's certainly production ready. It's a full featured language for sure. Personally I would use it, but at the moment the risk of breaking changes is rather moderate.
On Apr 15, 2:34 pm, Aaron Feng <aaron.f...@gmail.com> wrote: > Hi, > > I work for a large financial software company, and we are interested > in using Clojure for our new project. Due to the concurrent nature of > the project, we are evaluating three possible languages: Erlang, > Scala, and Clojure. This project will be a hosted solution, but > availability and performance is very important to us. We want to > deploy the project within 6 to 12 months, but the project will > continue to build out the rest of the functionality for the next 2 to > 4 years. We guesstimate that it will receive around 1M hits daily > initially, and it will continue to grow on a monthly basis. > > Due to the nature of the project, I'm only allowed to give high level > overview of the project at this time. > > We have a bias toward Scala and Clojure because they run on top of > JVM. The richness of existing 3rd party and open source libraries are > also attractive for us. > > The fundamental question for us is: Is Clojure worth our investment > in the current state? What are the possible risks? > > Also, if anyone has any thoughts on hiring Clojure people, it would be > greatly appreciated. > > Thanks, > > Aaron --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
