On Sep 3, 11:53 am, noahr <[EMAIL PROTECTED]> wrote:
> Any opinions on whether Clojure is solid enough to be used in actual
> production systems?
I have ~1000 lines of Clojure code at work (plus many more I'm no
longer using), not exactly "production" but in regular use for batch
jobs. The only
> Any opinions on whether Clojure is solid enough to be used in actual
> production systems?
I have no data yet, but I'm planning on putting a webapp on the web
using compojure just as soon as it's ready.
Allen
--~--~-~--~~~---~--~~
You received this message beca
On Wed, Sep 3, 2008 at 11:53 AM, noahr <[EMAIL PROTECTED]> wrote:
>
> Any opinions on whether Clojure is solid enough to be used in actual
> production systems?
So far, I've mostly used Clojure where I would have used a python,
perl, or ruby script in the past. So far, that's only amounted to a
We've not gone to production with Clojure code yet, but that day is
fast approaching. Every indication is that it's "ready for prime
time", at least in our circumstances. And yes, being able to drop
back into Java is a nice escape hatch to have (although we've only
employed it once in a very con
Chas,
Did that edge case ever come up on the list? If not, would you mind
sharing now?
-Matt
On Sep 3, 2008, at 1:46 PM, Chas Emerick wrote:
>
> We've not gone to production with Clojure code yet, but that day is
> fast approaching. Every indication is that it's "ready for prime
> time", a
Any opinions on whether Clojure is solid enough to be used in actual
production systems? Obviously it's JVM based, which is, and hopefully
any issues would be caught per normal testing, and fixed or worked-
around, but wondering what general thoughts on the matter are. As a
backup plan I figure lo
