3 ms·
Really good work. I spent 15 minutes reading through this book over my first cup of coffee this morning. I stopped using Clojure about 5 years ago, after two l
by mark_l_watson 8y ago
Really good work. I spent 15 minutes reading through this book over my first cup of coffee this morning.
I stopped using Clojure about 5 years ago, after two long consulting jobs using Clojure. I decided Clojure was not a perfect fit for me (and, really, neither is Common Lisp, Racket, and Haskell - more favorite languages) but I am very happy to see the Clojure ecosystem still creating such great tools around the language and functional composition.
- jdhorwitz 8y agoWhat have you found is the perfect fit for you?
- mark_l_watson 8y agoNothing. I use Python for deep learning but don’t care for the language. I prefer Lisp languages, most comfortable with Common Lisp but love the ecosystem around Racket. Love Haskell but I am in a many year learning curve.
- rlander 8y agoNo love for Pharo? ;)
- mark_l_watson 8y agoI play with Pharo about once a month. Love but no real amount of time spent with it anymore. Good language and platform, very energetic community but it is a small community.
- rlander 8y agoSame here. It's been on my "someday I´ll use it on a real project" list for 10-ish years. From time to time I boot an image, play around, cry a little, get back to Python.
- marai2 8y agoCould you describe what the deficiencies or rough edges were with Clojure and Common Lisp in your experience with them?
- mark_l_watson 8y agoI tend to do bottom up repl based development. For reasons that frankly I don’t remember, I compared the experience in Common Lisp to be better. And, I was always put off a little by the stack traces. I donated to Rich for the early development of Clojure, and it is a fine language and ecosystem, but it is just not a favorite language for me. I gave Clojure another look more recently because of the bindings for the mxnet deep learning library, so I guess I didn’t completely drop it.