14 ms·
I'm absolutely in love with Clojure. That being said, it does suffer the Lisp curse, in that I now feel unable to function in previous languages that I was pro
by nanomonkey 6y ago
I'm absolutely in love with Clojure.
That being said, it does suffer the Lisp curse, in that I now feel unable to function in previous languages that I was proficient in because I'm now allergic to boilerplate and the inability to create my own syntax when needed. Lots of Python jobs out there that I feel like I should be pursuing, yet I just can't seem to get excited anymore by non-lisp languages.
Wish there were more Clojure job opportunities out there.
- kazinator 6y agoDon't be surprised, though, if you discover you're not able to function in an actual Lisp, either.
- nanomonkey 6y agoHa! I was going to write more about how I no longer enjoy Common Lisp also, but I didn't want to step on more toes than I already had. Don't get me wrong, Clojure has it's difficulties. Simple things are sometimes difficult to figure out how to do the correct way...and being hosted means you end up having to know far more than I would like about Java or Javascript.
- shivekkhurana 6y agoAre there any objective reasons behind not "enjoy"ing CL any more?
- ledauphin 6y agoeducated guess: lack of persistent data structures.
- nanomonkey 6y agoThis too.
- shivekkhurana 6y agoBut there are libraries that fill this gap, like https://common-lisp.net/project/fset/ https://common-lisp.net/project/fset/
- nanomonkey 6y agoI've come to realize that I like opinionated languages. Common Lisp allows and implements nearly everything imaginable which I find disorienting. I've also found it hard to work on a team where everyone is coding in a different style, and has their own opinion on correct usage of the language. This is one of the reasons I fell out of favor with Python. I would write correct code that was often times quite performant, but would be chastised for being "hacky" (when I would write SQL views, instead of using the ORM), or unmaintainable, when I'd utilize functional constructs when others thought an OO or imperative approach was more appropriate. And every engineering manager, library maintainer, and linter has their own preference that I felt like I was bouncing between for arbitrary reasons. Clojure's choices seem to well thought out, consistent and coincide with how I like to attack problems.