Please don't start new threads as replies to other threads.
--jason
On Aug 11, 2008, at 11:30 AM, Dan Sline wrote:
All,
I know that developing in Groovy (and Grails) can reduce the costs over standard Java and Web Development. I have a friend of mine, who is evaluating whether to pitch to upper management to do his next project in Groovy/Grails.
Are there any studies or examples that you have to help justify/quantify a cost savings (which I know there is a cost savings) to develop in Groovy from both the initial development phase and maintaining the Groovy codebase in the long run? Since Groovy is dynamically typed, were there any additional test cases that you needed to run to prove that the code behaved as expected?
Thanks in advance,
Dan Sline