[tom_b]

I remember being at the first Clojure/conj - I had just spent some time learning a bit of Common Lisp and stumbled onto the conference announcement somehow.

This was very fortunate for me - after attending the conj, I was able to use Clojure at work to sneak in some FP on the readily-available JVM platforms. I later used it to do some internal REST-API work. The code for that project has run for years without modification or error.

For whatever reason, I also discovered that thinking functionally with Clojure worked so much better and naturally for me than object-oriented design methods. While I have drifted away from Clojure over the last couple of years, I find that my problem solving mind is much better in other languages because of the time spent thinking functionally with Clojure.

[adamkl]

"The code for that project has run for years without modification or error."

To follow up on this point, if you ever need ammunition to sell the use of Clojure inside an enterprise level organization, just show your Chief Architect the graphs of code stability over time for Clojure (pg. 71:26) and ClojureScript (pg. 71:30).

After working with JavaScript (not trying to bash) for the last few years, the idea of stability has become top of mind for me.

[O_H_E]

Wow, I didn't expect such differences compared to Scala. These graphs need a study on their own.

[dfinninger]

Looking at it, seems like the Scala code base found some stability in 2011?

This could be a factor:

> On 12 May 2011, Odersky and collaborators launched Typesafe Inc. (later renamed Lightbend Inc.), a company to provide commercial support, training, and services for Scala. [0]

[0] https://en.wikipedia.org/wiki/Scala_(programming_language)

[puredanger]

https://erikbern.com/2016/12/05/the-half-life-of-code.html

[adamkl]

https://www.groundedsage.dev/posts/the-clojure-mindshare/#he...