Skip to main content

Learn about Groovy and Grails from the experts!

Posted by johnsmart on February 17, 2009 at 2:02 PM PST

If you are a Java developer considering a new web development project, you may well be tempted to try out Grails, one of the most promising new frameworks to hit the Java development scene over the last few years. And you would do well! But, as we all know, book learning and online tutorials can only take you so far.

If you are interested in learning about Groovy and Grails in more depth, and live in Colorado or Virginia, you would do well to take a look at the training courses offered by Scott Davis (author of Groovy Recipes: Greasing the Wheels of Java and Mastering Grails, both great books) and Andrew Glover (co-author of Groovy in Action and Practically Groovy, and all-round cool dude). The course material looks refreshing and up-to-date, and both of these guys really know their stuff.
Check it out!

"Probably the best training course I've been on."..."Not just how to write Java code but the 'business end' - how to build, test, deploy, manage and monitor"..."One of the best and most useful courses I have attended. And they didn't even try to sell me anything!" - Get up to scratch with the latest in Java tools and best practices! Sign up on the 2009 season of the Java Power Tools Bootcamps.

Comments

samokk: What can I say? I agree entirely on. Perhaps that grails is simply not delivered to the adult age for large projects? I hope...

Hey, just an additional comment to second felipegaucho. I would totally bet that scottdavis99 has never ever really tried grails on a real-world project, that involves writing MAINTAINABLE unit and integration tests, 15+ people-team, continuous improvement and refactoring, interaction with different systems, etc. And this IS TOTALLY FINE ! I would just appreciate it if people stopped religiously promoting grails. Grails is fine for some stuff, but real-world projects ARE A PAIN with grails. I am currently working on a big welles project for a telco company. We are TOTALLY regretting the choice of grails. Each small stupid refactoring is a pain, the errors are not explicit, the stack traces are polluted, the unit tests take forever to run (30 second startup overhead, this is _GREAT_ when you try to work in a TDD-fashion), the framework has weird, unexpected bugs, the assumptions made by the framework are simplistic, you cannot easily access the underlying features whenever you need them, using the hibernate builders for something else than hello world leads to weird closure hacks, etc etc etc.. No, seriously, grails is a PAIN for us, and we are now progressively adopting the java minding instead. So the 10x productivity boost everyone brags about is just plain RE-LI-GION. So pleaase. grails is great, but for hello world apps.

Hmm, Felipe, I'm sorry that you didn't have a good experience with Groovy and Grails. I'd like to politely disagree with your assertions that Groovy and Grails are only suitable for "toy" applications. The folks at Wired, LinkedIn, SkyTV, TriMet, Mutual of Omaha, and many others have used these technologies with great success, and in anything but "toy" applications. That's the beautiful thing about our industry, though, isn't it? There isn't one language or web framework to rule them all. If these didn't work out for you, I hope that you were able to quickly move on and find the perfect fit somewhere else.

I used both Groovy and Grails in my last few projects.. fro mthat experience, just a friendly advice: 1) Grails is useful only for simple projects or the ones you can keep the GUI as simple as possible and the ones you can reflect the database direct in your GUI. Anything more sophisticated will fail with Grails. 2) Groovy is only for ultra-simple projects or test purposes.. actually, groovy is nice for regular testing The IDE and other tools fails miserably in supporting Grails and Groovy development and the complexity of such languages under a heavy project is not acceptable at all :) after some time working with that technologies in real world project I started to joke with friends about a "simplicity trap", where technologies only perform well under very simple toy examples..