I studied Clojure and I hope really cool stuff comes out.
When Rails came out it solved all kinds of new problems. For one, by using metaprogramming a whole bunch of files were eliminated. As soon as Rails came out I was much more productive than I was with Tapestry or Wicket. Not so with Clojure.
The metaprogramming capabilities in Clojure greatly exceed those of Ruby, so that's a bit of a weak argument if you're impressed by things of that nature. Also one shouldn't forget about Clojure's concurrency model and functional purity which lend themselves to correctness and scalability.
Just because it doesn't necessarily better solve your class of problems doesn't mean it's unsuitable for other people's.
Comments
I studied Clojure and I hope really cool stuff comes out.
When Rails came out it solved all kinds of new problems. For one, by using metaprogramming a whole bunch of files were eliminated. As soon as Rails came out I was much more productive than I was with Tapestry or Wicket. Not so with Clojure.
The metaprogramming capabilities in Clojure greatly exceed those of Ruby, so that's a bit of a weak argument if you're impressed by things of that nature. Also one shouldn't forget about Clojure's concurrency model and functional purity which lend themselves to correctness and scalability.
Just because it doesn't necessarily better solve your class of problems doesn't mean it's unsuitable for other people's.
"bit of a weak argument if you're impressed by things"
I'm impressed by results