Skip to content
0:00 / 0:00

#clojure#richhickey#stuarthalloway

Clojure Turns 15 | Building Nu Engineering Meetup #03

Building Nubank

22K subscribers • 2 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.

Beginner. No background in the topic needed.

15K views3 years ago1 recommendation

Programming languagesHistory and cultureLisp and ClojureHistory of computing

Rich Hickey, Stuart Halloway, and Alex Miller discuss the past, present, and future of Clojure in a round table celebrating its 15th anniversary.

In this special edition of the Nubank Engineering Meetup, we invited the Clojure team to a round table celebrating 15 years of Nubank's favorite programming language! Back in 2005, Rich Hickey funded the development of Clojure during a sabbatical, implementing 100% of the language before releasing it in 2007. Since then, Rich's team has grown and Clojure has become one of the most loved programming languages out there (e.g., 3rd place on the 2022 Stack Overflow Developer Survey) with adoption in many industries. Jaret Binford hosted our round table conversation about the past, present and future of Clojure. You can learn about key moments in the development of the language from some of the people that were there as it happened. Our guests: Rich Hickey, Author of Clojure & Distinguished Software Engineer Stuart Halloway, Distinguished Software Engineer Alex Miller, Principal Software Engineer Michael Fogus, Principal Software Engineer We at Nubank are proud to be the global sponsors of Clojure and invite you to this celebration!

Why it's here

1 person recommends this

What people say. Recommended as a fascinating historical retrospective on the creation and evolution of Clojure.

u/alexdmillerin r/Clojure • Recommends

Clojure Turns 15 round table video

u/slifinin r/Clojure • Mentions

On “New Clojurians: Ask Anything - November 21, 2022”

On another tangent, if you watch 15 years of Clojure: link to this video You can see that when asked Rich Hickey and the team think we're not capitalizing on the live-ly-ness of the language enough as a community And again I think this is a trust/culture issue, of the few Clojure companies I have been in, there has never been the ability to REPL into a machine, even staging machines to debug issues We just treat Clojure like another dead language in production, if there was trust and culture buy in there we could build access control, audit logs etc for REPL access