Slides can be found here: github.com/reborg/euroclojure-2014/blob/master/clojure-beasts-euroclj-2014.pdf
If you started developing Clojure you should also have realised how core.clj is a useful and important source of information along with the standard documentation. It will also come the time to look at how the runtime RT.java is implementing some functions that are not performing so well. Compiler.java and the compilation process is also an area worth looking at. But these are huge classes (2K+ loc) written in a funny style (for typical Java standards). Have you ever wondered why Clojure was designed like this? Why stack traces are somehow confusing? Would you like to contribute a patch but don't know where to start?
With this talk I'd like to take you on a journey through the Clojure sources. We'll see how Clojure was designed, what problems a Lisp on the JVM is typically facing with, what decisions were made and what was abandoned, what happens during initialization and what at runtime. Hopefully after the talk it should be clear to you why bigger projects are struggling with long startup times, why there is an elegant object model at the heart of a functional language and what improvements are in the pipeline to make Clojure better than ever.
Loading more stuff…
Hmm…it looks like things are taking a while to load. Try again?