InfoQ Homepage Presentations Improve Your Java with Groovy
Improve Your Java with Groovy
01:27:08
Summary
Ken Kousen demoes 10 cases when he says it’s better to use Groovy: XML (and JSON), JDBC, I/O (Files), Collections, Closures, Builders, AST Transformations, Meta-programming, Spock, and Gradle.
Bio
Ken Kousen is the President of Kousen IT, Inc., through which he does technical training, mentoring, and consulting in all areas of Java and XML. He is the author of the O'Reilly screencast "Up and Running Groovy", and the upcoming Manning book about Java/Groovy integration, entitled "Making Java Groovy". He is also an adjunct professor at the Rensselaer Polytechnic Institute site in Hartford, CT.
About the conference
SpringOne 2GX is a one-of-a-kind conference for application developers, solution architects, web operations and IT teams who develop business applications, create multi-device aware web applications, design cloud architectures, and manage high performance infrastructure. The sessions are specifically tailored for developers using the hugely popular open source Spring technologies, Groovy & Grails, and Tomcat. Whether you're building and running mission-critical business applications or designing the next killer cloud application, SpringOne 2GX will keep you up to date with the latest enterprise technology.
Mar 06, 2012
-
Related Sponsored Content
-
Related Sponsor
/filters:no_upscale()/sponsorship/topic/d7295235-717e-4e53-b057-e8f2b20f7838/MicrosoftLogoRSB-1650524400057.png)
Community comments
Very good talk... maybe I'll use groovy instead of scala
by Amihay Zer-Kavod,
Code
by bruno mendes,
Re: Code
by koby aharon,
Very good talk... maybe I'll use groovy instead of scala
by Amihay Zer-Kavod,
Your message is awaiting moderation. Thank you for participating in the discussion.
Thank you Ken for a very clear and down to earth talk and for reminding me what I liked about groovy when I first saw it a couple of years ago.
I've been trying to push Scala into my workplace for the last year, but I failed. Too many hurdles, since Scala is a big gun language, and can replace java altogether, but it introduces a lot of new concepts for OO developers to absorb (while being asked to be super productive). We just couldn't find the time for it.
So your talk led me to consider using groovy instead, and just allow its ease of use allow the guys both productivity and introduction to the more functional concepts out there, eventually, and for the entire shabang, I will still go with something like Scala, but for the getting some new concepts in (closures etc...) as well as some increased productivity, Groovy might be the way to go. One big thing still bothers me, and you mentioned it, the performance issue, when I check it, more then a year ago, it was very poor. Not sure it will past my tests today, but lets hope so...
10x again.
Code
by bruno mendes,
Your message is awaiting moderation. Thank you for participating in the discussion.
Great presentation, certainly made me look at Groovy with another eyes.
Is the code used available for download?
Re: Code
by koby aharon,
Your message is awaiting moderation. Thank you for participating in the discussion.
As tweeted by him a few days ago: " Source code for my InfoQ presentation is in GitHub repo for my book t.co/Lk4SgZWw in ch02/groovybaseball -- Ken Kousen (@kenkousen)"