Clojure being driven by the needs of Rich/Datomic may be true, I can't say for sure, but in my experience clojure development is driven by the need to solve real-world problems.
I agree, if it was more community oriented there would probably lots of cool ideas, exploring lots of other areas, but, for me, that's what other languages are for. And for what it's worth, they don't solve real world problems as well as clojure does.
I do wish Cognitect was more engaged with the community at large, but they've been solid stewards in my opinion, and all the features that have come since I started with clojure (1.6) have been extremely useful in real-world situations and has made my job easier and more enjoyable.
Comments
Clojure being driven by the needs of Rich/Datomic may be true, I can't say for sure, but in my experience clojure development is driven by the need to solve real-world problems.
I agree, if it was more community oriented there would probably lots of cool ideas, exploring lots of other areas, but, for me, that's what other languages are for. And for what it's worth, they don't solve real world problems as well as clojure does.
I do wish Cognitect was more engaged with the community at large, but they've been solid stewards in my opinion, and all the features that have come since I started with clojure (1.6) have been extremely useful in real-world situations and has made my job easier and more enjoyable.
I'm happy to make that tradeoff.