Is developer productivity higher on Ruby on Rails or Grails?

Question

Given that both Ruby on Rails (RoR) and Grails can run on the JVM (Java Virtual Machine), which language and framework enables equally competent and experienced developers to be more productive and roughly by what percentage? (i.e., deliver more business functionaity for the same amount of effort)

I know that Grails is easier for a Java developer to transition to. And I realize that the entire Java Library is available to a Grails developer. My question is regarding developer productivity in an environment where one runs on an JVM on Linux using the standard application servers (WAS, Weblogic, JBOSS, TOMCAT etc.). Note: JRuby will be used to enable RoR to run on the JVM.

I would requests answers from those that have done significant web applications development using both ROR and Grails.

Answer 1

If all you're looking for is a 75% answer: grails

I've done significant development on both platforms, though my major rails experience ended about a year and a half ago (before rails 2.x was released).

I've been heavily involved in grails development since grails 0.5.

The answer really depends quite a bit more on the developers and infrastructure that will be available to work on the project. If you're looking to deploy to a standard java app container (like Tomcat), I think that Grails is the better choice. If you're looking to do something with mongrel/rack/pound/etc. Pick rails.

If there are particular gems/jars that fit your business problem, that would obviously affect your decision.

The choice of Grails for me isn't so much because I think that it's better at solving all kinds of problems, but more because I like the grails developer community better and I like the groovy language a little more.

I've also found grails to be an easier sell to the places I've worked at over ruby/rails. There are many more java shops around here and it's less of a leap for them to make that transition.

This is a personal preference and I could easily see someone else going the other way.

Rails has quite a few things going for it, and I think the test driven development story there is much better (though I'm working on trying to fix that).