Did you do Ruby prior to Clojure? It's interesting to see you making the jump to Ruby right as I'm heading down the opposite direction on the Polyglot Interstate.
I jumped on the Ruby ride in mid-2007 and the libraries lacked polish; Rails had performance issues, RSpec its hiccups, and Cucumber was quite a frustrating experience, yet there seemed to be so much potential there that I staid on.
Now Clojure seems to be going through similar evolution. Libraries and frameworks like Enlive, Pinot, and core.logic display immense promise but the full stack feels still a bit wobbly.
But it is as you say; different situations and people need different tools. I still do most of my web dev client work with Ruby but I'm itching to try out Clojure for more complex data processing and, when the libraries mature, full-stack web development.
EDIT: Oh, and I'm with you on the stack traces... Good thing there's an update due in Clojure 1.4.
I picked up Ruby just after I picked up Clojure (and well after I picked up lisp in general). I still dislike the ruby community's lack of maturity, but seem to be coping better with it these days. #lolbundler & rvm are still terrible compared to lein though, which often frustrates me a lot.
I jumped on the Ruby ride in mid-2007 and the libraries lacked polish; Rails had performance issues, RSpec its hiccups, and Cucumber was quite a frustrating experience, yet there seemed to be so much potential there that I staid on.
Now Clojure seems to be going through similar evolution. Libraries and frameworks like Enlive, Pinot, and core.logic display immense promise but the full stack feels still a bit wobbly.
But it is as you say; different situations and people need different tools. I still do most of my web dev client work with Ruby but I'm itching to try out Clojure for more complex data processing and, when the libraries mature, full-stack web development.
EDIT: Oh, and I'm with you on the stack traces... Good thing there's an update due in Clojure 1.4.