hickey

Simple, in the way Rich Hickey advocates, means the opposite of complex, which means that things are woven together.

Rich Hickey released a few things for Java-Lisp interop before he decided to start over completely with Clojure.

Finally, there may be no better software design talks than Rich Hickey talking about designing Clojure.

I donated $100 so that Rich Hickey can continue working full-time to make Clojure even better.

And Product Hunt increasingly feels like some huddle of startup guys in the valley smiling at each other over the latest do-hickey they made.

Rich Hickey is amazingly prolific; even if this only supports an hour or two of his work, that translates into very real improvements to Clojure.

Rich Hickey has spent 3 years of his life creating Clojure.

I infer from the post that Rich Hickey still desires to spend the bulk of his time doing core development of Clojure.

I hope Rich Hickey is the former, clojure speaks for itself on the latter.

Someone has to decide whether building a particular new bridge or hospital is more or less important than Rich Hickey building Clojure or Monty Widenius building MySQL.

Rich Hickey is a pragmatist, and he gets that.

Rich Hickey has been criticized for that repeatedly.

As Rich Hickey often says, he is a "practitioner." He wants to Get Things Done, and Clojure reflects that.

When Rich Hickey talks about simple, he is referring to tight coupling, "death by specificity" and hard to understand concurrency.

Sounds Hickey-tier simple to me, especially compared to your advice of "just use and configure Nginx".

What you’re talking about is what Rich Hickey and Stu Halloway call “complicated”, which is different from what they call “complex”.

Hickey is in favor of clear multi-tasking conventions, but go code can do it many ways.

Maybe the marketing isn't great, but Rich Hickey's talks plus some successful use cases would be enough to drive more people into it (IMO).

It's interesting she mentioned Rich Hickey's simple made easy talk.