http://blog.fredjean.net/articles/2006/09/07/the-four-pillars-of-groovy-adoption en-us 40 Frederic Jean's Random Thoughts <p> Groovy in and of itself is a very good language. We have been using it for many years now in our shipping products. Yet, there is still to be a ground swell of adoption of the language. Part of the problem may be the relative obscurity of the language, or a misconception around its "scripting" nature. I do believe that we need to do some evangelism on the language. </p><p> Even so, I see four different pillars that the community can leverage to drive adoption. Out of these four, two are Groovy specific: </p><ol> <li>JSR-223 providing a standardized way to call dynamic languages within Java code.</li> <li><a href="http://www.springframework.org/">Spring 2.0</a> treating dynamic languages beans as first class citizen within the framework. You can define you beans in groovy without compiling it and inject it into another Spring bean.</li> <li><a href="http://www.grails.org/">Grails</a>. Brings many of the principles that are making Ruby on Rails successful to the Java platform without the, er, attitude displayed by the Rails core team.</li> <li><a href="http://www.manning.com/koenig/">Groovy In Action</a>. Having one or more books on a technology is usually a milestone toward wider adoption of a technology. I will simply point to Dave Thomas's books on Ruby (Pickaxe 1 and 2) and Rails (Agile Web Development with Ruby on Rails) as examples.</li> </ol><p> Groovy In Action will probably have the most immediate impact since having a book available in bookstores will increase the visibility of the language. It is currently going through Manning's early access program (MEAP), but the material so far is pretty good. </p> Thu, 07 Sep 2006 22:48:06 +0000 urn:uuid:558cfcea-b02c-4579-a108-027efd665186 fred@fredjean.net (Frederic Jean) http://blog.fredjean.net/articles/2006/09/07/the-four-pillars-of-groovy-adoption Groovy http://blog.fredjean.net/articles/trackback/47