On Mon, 2015-04-13 at 14:33 +0100, David Dawson wrote: > […] > Eclipse support is something of a sore point right now. All our commercial > discussions say that it's got to be there for Groovy to continue to win. > Grails is still a big driver, although not as dominant as it once was, and > having a Grails IDE does support adoption of that framework. Intellij > alone > just isn't enough.
[…] I shall be blunt. Unless something changes pdq, Grails is irrelevant to Groovy traction. The drivers for Groovy are Spock and Gradle. Gradle Inc. has ignored the Pivotal Groovy and Gradle support for Eclipse in favour of developing something new from scratch. This may or may not be a good thing, but at least it is happening. JetBrains have as good support for Groovy and Gradle as one could ask for. NetBeans support isn't bad. Emacs (the one true editor) and VIM (the scouring powder) have Groovy support if not Gradle support. Spock, and Groovy rely on Gradle Inc and community support unless some organizations such as Netflix and others give as well as take. From what I hear, this may actually happen. I hope it does. Groovy needs resource from those that make a profit by using it. Enlightened self-interest and all that. -- 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
