On Mon, 2011-11-07 at 17:07 +0000, Kevin Wright wrote: [ . . . ] > Because Groovy had significantly different goals, James wrote it to be a > lightweight glue & scripting language that would support core Java work, > not something that could realistically be considered a replacement or used > anywhere that performance was at all important.
It seems that Groovy is veering rapidly to the optional typing camp rather than dynamic typing camp (which it was already in of course ot overloading wouldn't work. There is Groovy++ and the new Grumpy Mode in the mainline Groovy. Basically whatever James might have wanted in 2003, Groovy has moved on and become something much more than it was. You don't have to use Groovy, or even like it, but to hang an 8 year old millstone around it seems a bit disingenuous. [ . . . ] > "Tooling" means a great deal more than how friendly the Eclipse plugin is... > > If I have to fire up half of the eclipse IDE in my Continuous > Integration/Deployment server just to build the thing, and if I can't build > it at the command line, and if I can't use Maven/Rake/Gradle/SBT/whatever > with it, then I'm afraid I'm going to have to take any claims of "better > tooling" with a particularly large grain of salt. Indeed. I wonder why it is that the Intellij IDEA SBT plugin always forces the SBT window to be open and shown, none of the other tools do that, they always revert to the last known state. If the SBT folk want to be taken seriously they need to fix this. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
