Groovy supports creating Domain Specific Languages. A DSL is simply a mini programming language tailored to a specific situation or domain. The idea is to hide the characteristics of the underlying programming language as much as possible (in this case, Groovy/Java), and let the vocabulary of the application domain shine through.
DSLs are nothing [...]
One of the major benefits of using Grails as a web platform is how almost everything can be written in a single language — Groovy. No more switching gears between language constructs. Everything’s Groovy.
For any standard Grails app, the error log is called stacktrace.log by default. On some servers, it ends up in the config folder (rather than the logs folder) by default, so it’s hard to find. Also, with a fixed name, all apps running on the same server would share the same log. [...]
First choice: JetBrains IDEA 7.0 (with 8.0 coming shortly). Possibly a good second choice: NetBeans 6.5 (new). Last resort remains: Eclipse.
We’ve started contributing back to the Grails open source project. First up: furthering the cause towards an initial release of a jQuery plugin (http://www.grails.org/jQuery+Plugin). Also, the next release of the Jasper Reports plugin (http://www.grails.org/Jasper+Plugin) should make life easier.
I am currently leading the charge for our clients with Java-based web applications to adopt Grails (i.e. Groovy on Rails). Grails (www.grails.org) has recently achieved its official 1.0 release, just behind the 1.5 release of Groovy. We’re seeing a 10-fold increase in productivity by using GSP (Groovy Server Pages) over JSP (Java Server [...]