> We rolled back to Java many such critical paths just to be able to maintain them I guess that's what I see as one of the advantages of Groovy. You can do ult

> We rolled back to Java many such critical paths just to be able to maintain them I guess that's what I see as one of the advantages of Groovy. You can do ultra rapid implementation of something with minimal code and then as it becomes more critical you increase its type safety by adding first Groovy type hints, but further along that curve, convert it fully to Java or another statically typed language. So what you describe as a problem I see as sort of, optimal workflow, and the real problem is being forced to universally choose one or the other in other languages.