Dean Wampler discusses the state of Scala: the big changes in 2.8, the Scala on .NET, concurrency and parallelism with Scala and Akka, and experiences with adoption of functional languages.
Paul King discusses the state of Groovy and its maturing ecosystem which includes IDE support, static analysis tools, testing frameworks and the GPars library for concurrency.
Emil Eifrem explains graph databases, what domains they fit well, and the state of Neo4j. Also: how graph databases stack up against RDBMs.
Rich Hickey explains the ideas behind Clojure 1.2's new polymorphism constructs deftype and protocols. Also: Clojure 1.3 features such as faster arithmetic and future features like Pods.
Yehuda Katz talks on how Rails 3.0 has been received by the community, what are the differences compared to other similar frameworks, the impact of having different Ruby implementations, and what’s coming in Rails 3.1.
Mariano Guerra talks about Efene, a new language that targets the Erlang VM, which attempts to provide nicer syntax than Erlang.
Ulf Wiger explains the origins of some of Erlang's core principles and how they're even more relevant today. Also: a look at the strengths of Erlang, Clojure and Haskell.
Kresten Krab Thorup and Robert Virding discuss the origins of Erlang, the state of the Erlang VM, integrating native code with Erlang etc. Also: the challenges of running Erjang/Erlang on the JVM.
Scott Chacon talks about the technologies that power GitHub (Erlang, Redis,...), and the benefits of Git as a version control and as a storage system.Also: ShowOff, Scott's JS-based presentation tool.
Kevin Rutherford talks about the challenges of refactoring Ruby code, and his open source tool 'reek' which automates the discovery of certain code smells in Ruby code.
Martin Fowler and Paulo Caroli discuss testing, continuous integration and continuous deployment, as well as DSLs and REST.
Tom Preston-Werner introduces Git and GitHub and answers some questions about GitHub's architecture and features. He also talks about its development process and explains that using Erlang was instrumental for making it robust. Kenneth Lundin then talks about the decision of Erlang/OTP team to move it to GitHub and how it helped increasing contributions from the community.