On the importance of language idioms

Venkat has a very nice post on the importance of language idioms.  He starts with a small Java Swing application and transitions it to Groovy, JRuby, and JavaScript.  I can’t get enough of this kind of stuff, because it shows just how easy it can be to make the switch from Java to a dynamic scripting language (and back).  I, of course, think the Groovy version is the best for me because it’s so similar in feel to the Java version.  This is a huge win for me because it makes context switching simple and allows me to choose the language that is best for the problem I’m trying to solve.  Really, Groovy is even better than that, because I can mix in static AND dynamic typing, so I can basically get the best of both worlds right in one.

This entry was posted in Agile Processes and tagged , , , . Bookmark the permalink.

2 Responses to On the importance of language idioms

  1. HamletDRC says:

    So, can you provide Stuart Halloway with a compelling example of when to mix static and dynamic typing? The comments on his post contain some examples:
    http://www.relevancellc.com/2007/5/16/groovy-and-grails-three-worries

  2. I would only be able to echo the things that Graeme and John already said on Stuart’s blog. Personally, I just feel comfortable with the idea of being able to type sometimes and not others. To me, it just feels right to go ahead and type my domain classes but not use typing as much elsewhere.

    Stuart is probably right that mixing static and dynamic typing wouldn’t be enough to choose a language on, but that’s only one little nicety in Groovy.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>