Today marked the first day of the Groovy/Grails Experience, also known as 2GX, in Reston, Virginia. The conference spans three days and includes forty 90-minute sessions, panel discussions and code workshops. One of the first sessions of the day was Venkat Subramaniam's "DSL In Groovy." Venkat provided a thorough discussion on DSLs and how Groovy eases the creation and usage of them.
Grails 1.0 has been released. InfoQ spoke with Graeme Rocher, Grails project lead and co-founder, and CTO of G2One about the release of Grails 1.0 to deliver in-depth coverage about the feature-set, maturity, ease of use and future plans for Grails.
Recently, there has been a lot of debate around the usefulness Maven, which is a Java-based build and dependency management tool being used in many projects. InfoQ took a closer look at this debate to understand what issues are being encountered, and what has resulted from the debate.
Many developers faced with too many choices when selecting a web framework prefer to make the easy choice of using the framework they have used in the past or build their own. This is especially true for Java frameworks, as Neal Ford finds out; he also puts this paradox of choice in the context of other languages and draws some interesting and debatable conclusions.
Groovy project manager Guillaume Laforge discusses the history of Groovy, it's relationship to Java, where Groovy fits into Java development, how Groovy compares to Ruby, how Groovy enables domain-specific languages, and what future Groovy development will focus on.
Dynamic language support is becoming an increasingly common part of Java IDEs. NetBeans 6 has Ruby integration, Eclipse has the DLTK and Aptana, and IntelliJ IDEA 7 offers support for Ruby as well as support for Groovy and Grails (it made its first appearance in milestone 2 and will coming out of beta shortly).
This past week Matt Raible gave a presentation at ApacheCon comparing Java Web Frameworks. This is a follow up to a presentation he gave a few years ago. It is interesting to note the changes in the frameworks being evaluated.
Graeme Rocher announced Grails 0.6 which moves further away from "its Rails-like beginnings" but adds Spring WebFlow rich conversations.
JetBrains has released the second milestone of IntelliJ IDEA 7. Among the features of M2 are enhanced Groovy/Grails support, dependency analysis tools, and better Spring/Hibernate integration.
Marc Palmer, a Grails committer, posted about some of the common misconceptions that developers have about Grails, such as "Grails is not mature enough for me". Graeme Rocher followed up with his own list of misconceptions and questions, discussing where Grails fits in with JRuby on Rails and Ruby on Rails.
The Grails framework promises Rails-like productivity while leveraging existing Java knowledge, libraries and tools. With Grails' new releases, increased attention and a drive to 1.0, InfoQ has taken the opportunity to speak with Graeme Rocher, the project lead.
Java web frameworks are increasingly adopting the ability to change portions of a web application and see the results immediately without restarting the server. This capability reduces the cost of the compile-build-test cycle, and helps to compete with the features of dynamic-language web frameworks such as Ruby on Rails or TurboGears.
The Grails community recently posted some unscientific benchmark numbers comparing a simple crud app written in Grails and Rails.
The head of the JRuby project ponders the possibility of replacing the Groovy parts of the Grails web framework with JRuby. The head of the Grails project responds.
There are two trends playing themselves out in response to this question. First there is the concept of simply running the Ruby language and in turn Rails under the JVM. Bloggers have been discussing the other concept of creating comparable frameworks in Java that catch the secret combination.