Adrian Colyer, Juergen Hoeller, Mark Pollack and Graeme Rocher present SpringSource’s Unifying Component Model, current developments regarding Big Data, and betting on Grails.
Dierk König introduces GPars, Groovy’s library for concurrent programming, explaining a simpler and less error-prone way to use fork/join, map/reduce, actors, and dataflow in Java and Groovy.
James Williams explains how to create and manage Ratpack (a micro Groovy web framework) applications, and dealing with authentication, persistence and interfacing Grails apps.
Ken Kousen demoes 10 cases when he says it’s better to use Groovy: XML (and JSON), JDBC, I/O (Files), Collections, Closures, Builders, AST Transformations, Meta-programming, Spock, and Gradle.
Neal Ford emphasizes the fact that functional programming uses a different way of solving a problem, thinking about the results rather than the steps to make.
Andy Clement and Martin Lippert discuss the latest developments in Spring Tool Suite related to Java 7, Spring 3.1, Groovy, Grails, Gradle, and Cloud Foundry.
James Ward demoes building a Spring Roo application and a Grails one, deploying them on Heroku.
Guillaume Laforge covers the main new features in Groovy 1.8 –DSL with command chain expressions, runtime performance improvements, GPars, closure support, JSON, and what is to come in Groovy 1.9.
Peter Ledbrook outlines the differences between several PaaS providers from the perspective of building, deploying and running a Grails application in the cloud, demoing running Grails on Cloud Foundry.
Hamlet D`Arcy demonstrates some of the Groovy tools useful to increase productivity by generating code at compile time: Project Lombok and AST Transforms.
Jeff Brown introduces Groovy to Java developers, outlining the conciseness and expressivity of the language and covering various topics: GStrings, Closures, collections, builders, beans, etc.
Peter Bell explains DSLs, how to approach writing one, and especially how to evolve one over time using "fixing the API", "backwards compatibility", "versioning" and "automated evolution/checking”.