Live data from Hacker News

(next Rich)

clojure.org

31–40 of 158 posts

Re: (next Rich)

#31

i’m very grateful to rich for clojure, cognitect’s libraries/tooling, and datomic. all of these have been well maintained, stable, and backwards compatible over the years. although he’s no longer working on datomic, i really hope cognitect values growing it. it feels like such an improvement over sql to work with.

Could not disagree more strongly that Datomic is well maintained. I'd view it as a significant liability in any organization using it without very good reason. My experience operationally supporting Datomic at even a moderate scale was a total nightmare and soured me on the Clojure ecosystem as a whole.

Re: (next Rich)

#32
post #4

Thanks for everything, Rich. You inspired me repeatedly.

Don't think Rich Hickey is "retiring" retiring, just that he's retiring from Nubank and "commerical software development".

TFA: I look forward to continuing to lead ongoing work maintaining and enhancing Clojure with Alex, Stu, Fogus, and many others, as an independent developer once again... Retirement returns me to the freedom and independence I had when originally developing Clojure. The journey continues!

Re: (next Rich)

#33
Without Clojure and the immense effort of the community around it and ClojureScript, OrgPad would not be possible and the individuals on the team would probably be stuck in some academic or corporate structures instead of having basically a two-families startup/ company. So thank you Rich and thank you to everybody else, who supported You on the journey to create something that makes coding predictable, productive and almost fun instead of laborious work. ;-)

Re: (next Rich)

#34
I 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 retired and rewritten, though that was due to new requirements that included C++ interop.

In the end tracking memory usage and allocations got too hard and if you've ever written something that is time sensitive you'll know just how slow memory allocation is, so you could argue I made a poor choice but for the rewrite was easy to reuse the java libraries when we moved to java.

The harder part was porting the algorithm implementation code. The reason was that I chose a common lisp trick of first writing a DSL in Clojure that was then used to write the algos.

That was the one part that seemed worse in the rewrite as it became far more verbose and clunky.

But man was it fun, I learned more in a month than I often do in a year now.

Thanks Rich!! It's not often you get to experiment with cool tech and make lots of money doing it. I appreciate your work.

Re: (next Rich)

#35

Rich Hickey's talks inspired me to explore Clojure and functional programming in college. That led to a part of my career where I got to help advance an FP language (F#). Can't say it was a raging success, but it wasn't a raging failure either. Really happy things worked out the way they did, though. I still look back at my senior project, written in Clojure, from time to time and find it elegant in a unique way.

My experience was similar. I've built far more impactful things since then, but at the end of the day, the software that I'm most proud of was a calculator, of all things, that I made in Clojurescript. It was loosely based on the final chapter of SICP, and implemented an hilariously metacircular approach to transitioning the state of the register machine. Since the implementation was way more interesting than the actual application, I used Processing to visualize the register machine as if it were a rudimentary ALU (which it basically was).

If it hadn't been for Rich Hickey, or Clojure, I'm not sure I'd have the slightest inkling of how joyful and creative it can be to write software. It was an A+ experience, even if I'd be swiftly fired for trying to push logic like that into production.

Re: (next Rich)

#37
post #31

i’m very grateful to rich for clojure, cognitect’s libraries/tooling, and datomic. all of these have been well maintained, stable, and backwards compatible over the years. although he’s no longer working on datomic, i really hope cognitect values growing it. it feels like such an improvement over sql to work with.

Could not disagree more strongly that Datomic is well maintained. I'd view it as a significant liability in any organization using it without very good reason. My experience operationally supporting Datomic at even a moderate scale was a total nightmare and soured me on the Clojure ecosystem as a whole.

may i ask what you consider moderate scale in terms of daily/concurrent users? i’ve had no issue with small projects, but i’m curious to know where it starts falling over

Re: (next Rich)

#38
post #8

I wonder if he’ll still give talks. I don’t blame him if not, but he’s really good at it. “Simple made easy” was a classic even if everyone proceeded to ignore the practical advice contained therein. And “Maybe not” is my personal favorite, a great discussion of requirements/provisions and the downsides of option types.

I think Hammock Driven Development[0] deserves a spot in the classics! [0]: https://www.youtube.com/watch?v=f84n5oFoZBc

Because of your comment, I watched this for the first time. I agree that it deserves a spot in the classics.

For those who haven't seen it, in the presentation Rich talks about figuring out the problem before you work on a solution. It's definitely something that could be improved in myself and in a lot of people and organizations involved in software development.

Re: (next Rich)

#40

Rich Hickey's talks inspired me to explore Clojure and functional programming in college. That led to a part of my career where I got to help advance an FP language (F#). Can't say it was a raging success, but it wasn't a raging failure either. Really happy things worked out the way they did, though. I still look back at my senior project, written in Clojure, from time to time and find it elegant in a unique way.

My experience was similar. I've built far more impactful things since then, but at the end of the day, the software that I'm most proud of was a calculator, of all things, that I made in Clojurescript. It was loosely based on the final chapter of SICP, and implemented an hilariously metacircular approach to transitioning the state of the register machine. Since the implementation was way more interesting than the act…

I pushed another build of a Clojure service into production a few minutes ago. There are companies that use it as a primary language you know :)
Post reply on HN