I’ve discovered Clojure a few months ago and I must say that I’m really hooked on this programming language. I can’t seem to just leave it on the backburner and get back to business with some other language. However, I still have real work to do for the small business I’m part of and I’m not yet convinced about going all-in with Clojure.
I won’t lie to you… there’s someone else!
We’re getting started producing Web based applications for manufacturing businesses and we’re still exploring what would be the tools of choice for the future. So far, we’ve been using Meteor JS as our main development platform for a year or so. We’ve been able to make apps up-and-running quite easily and relatively fast considering our entry level experience in Web development.
My reason is telling me to go with what works (Meteor) and get insanely good at it… but I can’t seem to let go of Clojure. I know the reasons why I should go with Clojure (immutability, FP all the way, easy and predictable syntax, JVM deployment, etc.) and I can compare them to those for Meteor (massive NPM ecosystem, seamless client-server integration, authentification built-in, mobile apps, etc.). I do feel that the learning curve for Clojure is still steep, even though I’ve read tons about and experimented a bit with it… but Rich Hickey is pretty convincing!
So here are my questions:
- Has anyone here used Meteor and decided to go with Clojure instead. If so, why?
- What kind of stack would I need to get close to Meteor’s capabilities?
I know that even if I ever choose to stick to Meteor, I’ll try to learn Clojure on the side.
Can you convince me to do the other way around?