Aaron, we have been in production with Clojure since January 2009. We use it to drive a message bus which is asynchronous by nature and requires high concurrency. It's been very stable. Our app runs 24hrs a day 7 days a week and is fully redundant.
As far as getting Clojure resources, we have been mostly a Java company for the last 8 years but we had several projects using other tools (C, ....), high level and low level stuff. Aside from getting tuned to the functional approach, there's not been any other impacts on the learning curve except getting used to immutability. Once you pass over this (getting rid of the old assignment habit) the benefits are immense. That aspect of Clojure was the biggest obstacle we faced. All the other stuff in Clojure is easy to pick up along the way If you have Java resources, you can make them Clojure "enabled" in a couple of months. Creating non-academic code (ie code to be delivered in your project) and then reviewing that against other code practises from the Clojure community should allow your resources to grasp the thing while creating the base for the rest of your project. Hey Mibu, glad to hear that Clojure is not production ready yet, we are probably all dreaming around here :))))) Luc On Thu, 2009-04-16 at 04:14 -0700, André Thieme wrote: > I suggest you to use Clojure. > There is no more risk involved than with anything else. > Clojure supports in its current version all of Java. > It has very nice libs, macros, cuncurrency engine, etc. > Those are fully production ready features. My company > uses Clojure for production, and it meets our high > expectations. > > The only thing that could happen is that there will be > a breaking change. That means: your unit tests will > suddenly report errors in many places. > In such a case you can decide to either fix them, > or just have a policy of not updating Clojure. > No one stops you from downloading the newest Clojure > and just work with that. > That will give you all of what Java can do plus everything > that there is in Clojure so far. This is a lot. > So yes, I suggest you to go with Clojure. > > > On 15 Apr., 21:34, 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 > > > Luc Préfontaine Armageddon was yesterday, today we have a real problem... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
