Note that there are some explanatory texts on larger screens.

plurals
  1. USTed Naleid
    primarykey
    data
    text
    plurals
    1. COThere aren't any good references that I've ever seen besides the javadocs (http://grails.org/doc/1.1/api/org/codehaus/groovy/grails/commons/DefaultGrailsApplication.html). I also find looking at the Grails sourcecode very helpful. I also use this kind of stuff heavily in the build-test-data plugin to inspect domain object constraints and automatically generate test objects that pass the constraints if you're looking for examples (http://bitbucket.org/tednaleid/grails-test-data/wiki/Home).
      singulars
    2. COIf your standard at work is the JVM, chances are that you have people with Java experience (and probably not an equal level of ruby experience). In that situation, I'd definitely pick grails. That's my biggest reason for my preference now, the area that I work in (the midwest) has a much larger population of java devs than ruby devs and that's not likely to change anytime soon. JRuby's java integration isn't quite as strong as groovy's (no joint compiler, etc). From what I've heard of your situation, I'd pick grails.
      singulars
    3. COHeh, I knew that, that was part of the point :). Either of the frameworks is good enough that if you're looking for a single answer and don't have any other big driving factors to pick one over the other, you can be successful. For me, where I'm at, and with the community I work in. Grails is the right answer, for someone else in different circumstances, Rails would be correct.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload