"Am I just a Java fanboy?" - this is a good question. And it is one that Bill Burke does answer in his blog post Dynamic Languages: Rationalizations and Myths. But along with the post comes an overwhelming response, and insight into where we are heading as a community.
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.
Using the EC2 API is straightforward, but to make life even simpler Chris Richardson has posted a Groovy framework that can launch MySQL, Apache HTTP Server, a set of Tomcat instances and JMeter, as well as deploying web applications to Amazon's EC2.
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.
IBM Fellow and WebSphere CTO Jerry Cuomo talks about REST and Project Zero, IBM's new Groovy & PHP based RESTful app mashup / scripting / dev tool.
Over the weekend the Groovy team released version 1.5 which contains numerous Java 5 language additions, enhanced tooling support, and performance improvements. In conjunction with Groovy Project Manager Guillaume Laforge, InfoQ is running an article detailing the new features of the release.
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.
With its inclusion into OpenOffice as the VBA equivalent for that suite, Groovy has an opportunity to become something that Java will never be: a tool that business power users use to customize their office suite and build workgroup applications.
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.
With dynamic languages playing a role in JDK 6, the "Cool things you can do with Groovy" session was aimed at show casing the features of the Groovy language that can help make developers more productive.