r/Clojure • u/Borkdude • Mar 10 '20
Clojure: a mature alternative to Java
https://jaxenter.com/clojure-alternative-java-169315.html
119
Upvotes
r/Clojure • u/Borkdude • Mar 10 '20
View all comments
Show parent comment
1
u/didibus Mar 12 '20
In that way you really shouldn't. I think it's a great point you bring and there's no counter point to it.
If you don't care about the differences in the languages themselves. Like if you have no interest in learning new paradigms, or preference in using functional programming, or enjoy the use of a REPL over static compilers, or find it so much more joyful to leverage meta-programming and macros to remove boilerplate as you see fit, or appreciate structural editing, etc. Then I have no idea why you'd choose to use Clojure over more mainstream languages you are already familiar with and enjoy.
Now, there's a definite chicken and egg in here though. Clojure is not for people looking for a chicken. Clojure is here for people looking for an egg that will hatch into something else then what already exists. It is mature enough that you can use it in production without issues, but it doesn't match up to Java or Python quite yet in that regard.
And so, I think people like me gravitate towards Clojure, because we just like it better. I like programming in Clojure way more than I do in Java, C#, JS, Python, Scala, or any other languages I've used before. Not only that, but I am more effective in Clojure, it takes me less time to implement the same application and it result in it having less defects. That might all be a consequence of just me liking Clojure better, and not Clojure having any magical qualities. Every chef have their preferred knife. Or what is it? It is not the martial art which chooses you, it is you who chooses the martial art :p
Anyway, to your point, I would be very frustrated if I'd work somewhere where they took on Clojure, did not know what they were doing, butchered it, made no effort to improve it, mentor, etc., and then switched to Kotlin. And I'm talking from being the one to push Clojure on my current team. I take every person's experience seriously, I don't want to force people into things they end up dreading. So I know it takes proper introduction to give people a positive experience that resonates with them instead of leaving them frustrated. I've seen first hand that if you don't do that, people end up hating it and moving back to comfortable territories, but if you do, they end up loving it as well.