No one likes slow builds. How many times a day do you compile your application, click the run button? How many times have you cursed Maven, SBT, Ant, Grunt (even Gradle?) for being slow as hell? Maybe some of you even frantically run `clean` as a conditioned response to a broken build tool.
At Gradle, we aim at build happiness: there’s no reason why you wouldn’t expect the same quality standards for your build process as you would for your code. Builds are important, and actually crucial to developer productivity. As such, they can, and need to be optimized for performance. Gradle offers several ways to do this: incremental builds, continuous builds, daemon, task cache or build scans and we’ve recently put a lot of effort into making Gradle blazing fast.
Learn how you can make your build significantly faster, and reclaim your CPU for coding, not building!
Speaker: Cédric Champeau
Cédric Champeau is a core Groovy committer. He joined SpringSource, a division of VMware, in order to help developing the language. Prior to that, he spent several years at Lingway, a software editor, where he used Groovy in multiple industrial contexts including DSLs for natural language processing, scripting or even workflows.
He his currently working on the implementation of static type checking and static compilation for Groovy 2.0. You can find him on Twitter at @CedricChampeau.