At refactr
we believe in the value of connection, the
utility of agile processes, and the power of great ideas.
We are creating the next generation of software for
people who expect more from their web applications.
« How do you prototype? | Peer Code Review »
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 by Jesse O'Neill-Oine on Monday, May 21st, 2007 at 9:21 pm and is filed under Agile Processes. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Subscribe to weblog
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 ...on May 22nd, 2007 at 8:00 am
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.
...on May 22nd, 2007 at 9:05 pm