Re: [groovy-dev] I'll give a Groovy presentation at the Jazoon'08

Quoting Jochen Theodorou <blackdrag@...>:

>>> Also since there are
>>> notes I don't see the reasons why you should not build large frameworks
>>> in Groovy.
>>
>> Frameworks can benefit from strict checking by the compiler.   
>> Groovy's strength is to easily pull different things together. It's  
>>  a great "plug'n'play" language like Python. If you put the same   
>> amount of checks and ground work into it as you can do in Java 6   
>> (with annotations like @NotNull), then the advantage shrinks.
>
> so your argument against it that you have less compile time checks.. I
> would have expected other arguments, because that is an argument you
> can always give against any dynamic language. And look at Rails.. isn't
> that a framework and isn't Ruby a dynamic language? Of course the only
> counterpart in Ruby is then C, or maybe anything that is binary
> compatible.. like Ada.. and these language do not share as much as
> Groovy and Java do. Maybe that's a reason why it is so easy to switch
> here.. but then that is more an advantage.

Yeah, these pages ("Reasons not to use Groovy" and "What's Wrong With  
Groovy") are crap. I was trying to sum up a few points when other  
languages would be more suitable or stuff where Groovy is weak but  
what I got is ... uh ... well ... yeah.

Anyone got any points I should mention? Times when you felt Groovy  
just not adequate for the task? If not, I'll just drop these two.

Regards,

--

-- 
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://www.pdark.de/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email