I just got home from another Getting Started with Grails presentation. After using the framework for about six months, I still can't get over how easy it makes developing web-based Java apps.

One of the most overused metaphors in our industry is "reinventing the wheel." If I had a dollar for every framework that claims it prevents me from having to do so...well, let’s just say I’d no longer be in the industry. In fact, a recent search on Google for java framework "reinvent the wheel" produced more than 55,000 matches.

Now I certainly don't want to reinvent the wheel; I want to buy my wheels from the wheel store. But even if I buy a set of four, I'm not going anywhere with wheels alone. I need a vehicle on which to mount them, don't I?

Combining Groovy with Grails in analogous to getting the entire car...for free! I'm then able to choose whatever options and color combinations I want, (i.e., the business requirements my application must meet).

I know simplifying development through code generation scares some folks. You may be reluctant to do so, thinking, "Hey, I don't want to give up control." Because Groovy compiles to bytecode, you’re still using Java. Making use of Grails scaffolding for a "leg up" is useful, but not a requirement. Use as much or as little as you like.

I would add that knowing how to drive a car doesn't exempt me from having to understand how one works. What if it breaks down? Or better yet, what if I want to customize it? As programmers, we don't get a free pass. We still have a responsibility to know the underlying technologies (Spring and Hibernate), as well as programming best practices (OOD, TDD, etc.). In the end, Grails is simply another tool but one that when used correctly, is extremely powerful. Remember what Uncle Ben said just before that car-jacking? "With great power comes great responsibility..."