Transforming Software Evolution: Lessons from 10 Years of Clojure in Production
summary
Ten years of Clojure powering CodeScene produce concrete outcomes: Erlang prototype runs in two weeks vs two months in Java and uses 25% of the lines of code, immutable design eliminates setup-heavy tests so there are no test setup methods, and large-scale analysis (Linux kernel, 21M LOC) gets a 10x performance win by swapping map for pmap then using a clayool thread pool; multimethods and macros implement a DSL for targeted code-health directives.
AI-written summary · about
chapters (10)
- 0:0010 years of Clojure in production
- 3:17Psychology to code crime scene
- 6:06Functional programming matters
- 10:57Immutability vs cognitive load
- 15:12Zero setup tests
- 16:14CodeScene analysis problem
- 21:14Parallelizing code health
- 24:20Programmable languages
- 30:22Domain-specific languages in Clojure
- 36:22Reflecting on Clojure
related talks
55mTransforming Enterprise Development With Clojure
40mclojure is my favourite ruby
38mProduction Ready ClojureScript: Tales from the Frontier
41mClojure for Ruby Programmers
35mThrough the Looking Glass
40mProgramming Clojure, Smalltalk-Style
33mTo Clojure and back: writing and rewriting in Ruby
28mHow startups can move fast with Clojure