I really love Clojure. I dug deep on it for a while and got pretty good at it. But I haven't used it in years. The trouble with Clojure is it's very hard, bordering on impossible, to get it going in a work environment. It's very difficult to justify the cost at the management level.
It's also very difficult to build a grass roots movement amongst coworkers because the harsh reality of lisp languages is you pretty much need some kind of "paredit-like" capability in your editor to not go insane. So people are really turned off at both needing to learn a new language and editor functionality.
I'm glad I learned Clojure and lisps in general as they've made me a better programmer. I just wish I could leverage them more.
> Really? I guess things changed but I had 0 trouble setting it up recently.
I don't literally mean setting it up like on a dev machine. I mean getting it installed as the language to use to build new products at a company.
> Every major Editor like VSCode, Atom, Vim, Emacs has this.
Sure, but the problem is it's "yet another thing" they need to learn. They're already skeptical about learning Clojure itself because <current-language> works just fine. So dealing with parentheses adds to the hurdles. At least, in my experience. It will of course depend on the people involved.
It's also very difficult to build a grass roots movement amongst coworkers because the harsh reality of lisp languages is you pretty much need some kind of "paredit-like" capability in your editor to not go insane. So people are really turned off at both needing to learn a new language and editor functionality.
I'm glad I learned Clojure and lisps in general as they've made me a better programmer. I just wish I could leverage them more.