|
|
|
|
|
by t-crayford
5318 days ago
|
|
I think clojure is close in some regards, but running on the JVM really hurts me these days (startup time really hurts TDD as I do it). I also think clojure has too much syntax (for a lisp), and am not convinced modern programs should be written in lisp any more (though that's hazy). At the moment I use Ruby, which is much less frustrating than clojure ever was. (I seriously love the shit out of rspec). Last but not least: stacktraces. This isn't to say I think Ruby is better for all tasks etc, just that it fits where I am right now. Clojure is probably better for people with differing tastes to me. |
|
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.