What is the difference between grails and rails

SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy. See our Privacy Policy and User Agreement for details.

Comparing Grails Vs. Rails Both the frameworks have their own pros and cons. Choosing between the two depends on the requirements, the intensity of the development project and the features you are looking in a particular framework. The SlideShare family just got bigger. Home Explore Login Signup. Successfully reported this slideshow. We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads.

You can change your ad preferences anytime. Comparing Grails vs Rails. Upcoming SlideShare. Like this presentation? Why not share! JUG views. Embed Size px. Start on. Show related SlideShares at end. WordPress Shortcode. Next SlideShares. In a recent comment on my blog, Jared Peterson asked:.

A friend recently asked me "Can I solicit your honest, unadulterated opinion on Grails? I think it's awesome. There does seem to be some maturity issues, but I think it'll get there. The question is - how fast can Groovy become. It's similar to Rails and Ruby in that you start using Grails and you think "This Groovy thing is kinda cool, I'd like to learn more. You can learn enough to be productive in a single day.

That being said, I think there's also a lot of cool stuff going on with RIA. Rails is definitely more mature, but the environment is a pain to setup esp. Grails is very easy to setup for Java Developers. Grails needs a lot of improvement as far as hot deploy and stack traces.

It's probably Groovy's fault, but its stack traces are hideous - rarely pointing to the class and line number in the first few lines. As for hot deploy, it doesn't work nearly as well as it does with Rails. Even with its warts, Grails is simply awesome.

I don't like "test-app" as much as I like Rails' "test:units" or even better, "test:uncommitted". It seems to be widely realized that Rails has a better testing story. Groovy is extremely easy to learn for Java Developers. This article is an attempt to explore the capabilities of both languages and frameworks and compare and contrast their approaches to problems.

Ruby and Groovy are both dynamic languages. The primary focus of this section is to compare the language level and standard library features and capabilities. However, some references to the additional language specific frameworks will be unavoidable since they are sometimes the best demonstrations of the capabilities of each language.

One thing that I will keep out of this section are specific comparisons between the Rails and Grails frameworks, since I will devote another entire section to that comparison later. Ruby was created in and is a reflective, dynamic, object-oriented programming language.

Ruby is a single-pass interpreted language. Its official implementation is free software written in C. Though to be fair, other languages like Ruby fall under the umbrella of JSR Scripting for the Java Platform, and hundreds of other languages can compile to bytecode and run on the JVM. Groovy includes features found in Python, Ruby, and Smalltalk, but uses syntax similar to the Java programming language.

Stack traces are long and illegible.