[vorg]

> Because they shifted their focus to CloudFoundry only

Although VMWare/Pivotal said they were pulling their funding for Groovy and Grails in order to shift their focus to CloudFoundry only, that doesn't explain why they held onto Spring. Groovy/Grails and Spring were managed and promoted together, and the more likely reason is the Spring team didn't want Groovy/Grails attached and petitioned the VMWare managers to dump them. Perhaps the Groovy and/or Grails people were trying to take over in some way. Grails 3.0 released in March now bundles Gradle as well as Groovy and Spring from before, perhaps another predatory move. It could explain why Gradleware recently employed two of the retrenched Groovy/Grails developers from VMWare, to help in protecting their product against takeover by bundling.

[u04f061]

Hmm. Your points seem promising and I can't disagree anymore. Why this corporate world is so difficult to understand?

[tlong]

I personally haven't used grails much. But here's another good post from my friend David Estes: http://www.redwindsw.com/blog/2014-01-15-moving-from-rails-t...

[u04f061]

I am not a rails developer but I have seen that rails developer have alot of inertia and they won't switch to grails. Grails is only attracting Java developers who are fed up of exhaustive configurations. Unfortunately books written for grails also assume that you are switching from one of java to grails.