I can't really have a Groovy retrospective without mentioning memory. Over the last four years I have spent more time than any sane person should have to investigating memory leaks in production Groovy code. The dynamic nature of Groovy, and it's dynamic meta-programming presents different considerations for memory management compared to Java, simply because perm gen is no longer a fixed size. Jav
![Groovy Retrospective: An Addendum - Memory Usage and PermGen - DZone](https://cdn-ak-scissors.b.st-hatena.com/image/square/5993006dd3225869eb3a6b7b5347857c65f1dacd/height=288;version=1;width=512/https%3A%2F%2Fdz2cdn4.dzone.com%2Fstorage%2Farticle-thumb%2F2334503-thumb.jpg)