Fork me on GitHub
#clojure-dev
<
2018-12-04
>
alexmiller16:12:55

Dear wizened Clojure devs, Rich is working on some historical work about Clojure (which I cannot answer further questions about at this time :)

alexmiller16:12:26

He is trying to get a list of important and influential libs/tools from the early days of Clojure, and the people that worked on them

alexmiller16:12:27

I would appreciate any suggestions

bronsa16:12:21

how early are we talking about? 2009/2010?

danielneal16:12:04

Does overtone/Sam Aaron count - not a tool as such but I found his talks so engaging that they definitely drew me in to learning clojure

alexmiller17:12:28

earlier the better

alexmiller17:12:02

overtone - sure! we may end up not using everything but happy to have it

alexmiller19:12:02

well, technically there is history so… early history :)

😂 1
alexmiller19:12:14

prehistory is when Rich was in the hammock :)

2
dominicm20:12:48

BC, before clojure? BH before hammock? :thinking_face:

seancorfield20:12:20

FYI, we now have Clojure 1.10 RC 3 in production on all our servers!

gfredericks20:12:51

sometimes you find out about new clojure releases because sean's announcing results of using it in prod

👍 1
seancorfield20:12:32

I hadn't seen Alex's post go to the mailing list (still haven't) but I did see it on Google Groups on the web, which is where I replied that our test suite passed...

gfredericks20:12:47

the first half of your message made me hopeful you had put it into production solely on having seen it in maven central

dominicm20:12:42

Literally the deps.edn {:deps {org.clojure/clojure {:mvn/version "RELEASE"}}}

seancorfield21:12:29

It's almost stable enough to go production on master all the time! 🙂 Almost.

alexmiller21:12:46

that’s weird - I have gotten a weird bounce message the last couple times I posted to the google group, even though I see the post, and it gets views, and people reply to it.