As a schemer there are so many small things I would like to change that put me off using it for my personal projects, but regardless I have really enjoyed contributing to other people's Clojure projects. It is not far away from what I would consider a good starting position for my own perfect language.
(next Rich)
111–120 of 158 posts
Re: (next Rich)
#112Rich has to be my favorite thinker in this space, absolutely love his talks and the way he articulates things, and I often draw from his philosophies in my work But, I've always been turned off to Clojure by the lack of static typing (I know spec exists, but it's not really the same thing). I did a little project once to try it out, and even there I found myself spending time debugging basic issues like passing the w…
Re: (next Rich)
#113The impact of Clojure cannot be overstated. It's amazing to see how far it has come since its inception. You've inspired so many developers, including myself, to explore functional programming and think differently about software design.
Re: (next Rich)
#114Re: (next Rich)
#115https://www.youtube.com/watch?v=dGVqrGmwOAw
At that time I had been working with Java for years, both the conciseness of the code and the interactivity were flat-out amazing to me. It's saved me time and made me 100 times more productive.
Congratulations to Rich, I am also extremely grateful for his work!
Re: (next Rich)
#116Re: (next Rich)
#117Earlier quoted context omitted.
So you had to switch to C++ because Clojure / Java wasn't performant enough?
> because Clojure / Java wasn't performant enough Languages aren't "performant". You can write good or bad code in most languages, or code that isn't a good fit for a language. That said, there are languages which will make you incur certain penalties, as there is a price to be paid for automatic memory management with garbage collection, for example. These penalties generally do not matter except for edge cases (and…
Re: (next Rich)
#118I wrote my first trading system in Clojure because a few of the libraries we relied on were in java. It was 2011 and I'd had about 3 years of lisp experience. I got a bit of side eye from people when I told them I was using a relatively new programming language but the fact that it was based on the JVM, which alot of HFT firms were using helped make the case. We didn't use if for more than a few years before it was r…
> you'll know just how slow memory allocation is Just a small nitpick, but allocation is definitely not slow in case of the JVM, it is often faster than manually managed languages. It is a pointer bump only. All the necessary mechanisms of a GC does have an overhead, so your point stands, but not for the mentioned reason.
Typically in HFT We just want to avoid any full sweep garbage collection between 8am and 6pm
Re: (next Rich)
#119While, as is to be expected, I don’t agree with every decision made for Clojure, I find it to be an entirely pleasant Lisp to work with.
So, kudos to Mr. Hickey, and thanks for sneaking Lisp back into corporate America!