concept optional static typing in category groovy

This is an excerpt from Manning's book Groovy in Action, Second Edition.
It’s clear that Groovy’s success is related to its powerful runtime metaprogramming capabilities. When the Groovy team announced that Groovy 2 would support static typing, a lot of people were wondering why we did so. Groovy is, and will remain, a dynamic language, but it now offers optional static typing. This is in line with a general agnostic stance Groovy takes on style. Functional or imperative, static or dynamic, Groovy lets you decide. The objective of the language isn’t to force you into a particular style or paradigm but to give you options. It won’t lock you into a particular mindset, that dynamic languages are generally better than static ones, or vice versa.