Dan Sline schrieb:
> 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?
I think you should ask this on the grails user list. At last for Web
development you should get some data. If your doubts are about dynamic
typing, then you could maybe use some of the comparisons Rails vs. Java.
As fair/unfair they might be. There is for example
http://www.infoq.com/news/2006/11/tim-bray-intrinsics which is surely no
study. But I think the point, that a reduced code size reduces the
maintainance costs as well is something to think about. sure, Groovy is
not Ruby, but the code sizes are often comparable, and I know that a
program in Groovy often takes less than 40% of statements than Java.
Well, that's no direct help at all, but maybe a hint
bye blackdrag
--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead (
http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/http://www.g2one.com/---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
