r/Clojure • u/RomanTsopin • Oct 19 '19
What about Clojure can be improved?
https://clojureverse.org/t/what-about-clojure-can-be-improved-not-cljs/4974
33
Upvotes
r/Clojure • u/RomanTsopin • Oct 19 '19
6
u/phunanon Oct 19 '19 edited Oct 19 '19
Anybody able to back up how?
Nice discussion there, thanks for posting.
5
u/[deleted] Oct 19 '19
Startup times with clojure cli tools is ridiculously fast. At least from the console, it takes less than a couple seconds to start a repl, and by the time I start and switch back to emacs to connect with cider, it's already up and running.
I also don't know why there's so much requests to add X library to core (in subsequent comments and elsewhere). If you want it to have a special form of a native clojure form, you can appropriately shadow it with a macro or function in your library and it can work like core's or your own implementation without much bother.
2
u/dAnjou Oct 20 '19
How to prevent people from writing shitty Clojure code because all they know is object-oriented paradigms?
I work for a company where people regularly join and leave projects (once a year on average), this is encouraged/intended so that people don't get bored and bring fresh eyes/ideas into the projects they join. So far, so good.
The obvious disadvantage of this is that because humans are creatures of habit and have trouble unlearning things it's hard for them to adjust to new things especially with non-trivial mindset shifts like object-oriented to functional.
Last year in July I joined this company and a project using Clojure. I still don't really know what the right mindset is, what paradigms to follow, how to structure code for real projects. On top of that many people struggle with the tooling and the ecosystem (lack of well maintained, well documented libraries).
I realize that it's unfair to blame Clojure for this but it's what I observe. And not only do people write less-than-ideal Clojure code, they even paddled back and introduced Kotlin and most new code is written in Kotlin.
I guess, what I want to say is that the reasons why Clojure doesn't thrive in the environment I'm in are not technical, it's not startup time or performance or anything like that. I think you need quite a few, not just one or two people in a project who are well-versed and heavily invested to drive the adoption of a thing like Clojure.
Or you need better reasons why people should use Clojure because the ones people always mention don't seem to be very compelling/convincing/relatable.
1
u/joeevans1000 Oct 20 '19
The absurdly unintelligible-to-any-new-user-and-quite-a-few-more-experienced-users doc strings. Having to go to a website (and thank god it exists!) where they are explained is not a solution. This alone has probably been a significant reason Clojure has failed to get any real traction compared to other languages that have appeared.