Comments on: Grails vs. Rails http://www.jtict.com/blog/grails-vs-rails/ About programming stuff Sat, 19 Dec 2009 14:03:24 +0300 http://wordpress.org/?v=2.8 hourly 1 By: fabien7474 http://www.jtict.com/blog/grails-vs-rails/comment-page-1/#comment-2763 fabien7474 Thu, 03 Sep 2009 11:02:57 +0000 http://www.jtict.com/blog/?p=30#comment-2763 Thx for this article. I have been through all of the comments, and I can summariwe what REALLY MATTERS for me ONLY when comparing Rails and Grails Grails Pros - Groovy based on Java and Rails based on Java Fwks => It gives HUGE ways of extensibility, scalability and workarounds (if stuck with Grails). And I am a Java developer. Also, overloading is available (not in Rails) - Domain model centric vs Data model centric for Rails. No deal with SQL, changes to domain classes are automatically done in the DB Attrubutes in domain classes are defined in one file only and refactoring is easier - Grails has an expression language - Grails is faster than Rails (but needs more memory) Rails Pros - View layer is strong compared to Rails (RJS) - REST by default. - Rails is more mature : more doc, more help from the web, more stable?, more secure? - Easier to debug (Grails is known for cumbersome error messages) My winner: Rails...meanwhile :-) Thx for this article.
I have been through all of the comments, and I can summariwe what REALLY MATTERS for me ONLY when comparing Rails and Grails

Grails Pros
- Groovy based on Java and Rails based on Java Fwks => It gives HUGE ways of extensibility, scalability and workarounds (if stuck with Grails). And I am a Java developer. Also, overloading is available (not in Rails)
- Domain model centric vs Data model centric for Rails. No deal with SQL, changes to domain classes are automatically done in the DB
Attrubutes in domain classes are defined in one file only and refactoring is easier
- Grails has an expression language
- Grails is faster than Rails (but needs more memory)

Rails Pros
- View layer is strong compared to Rails (RJS)
- REST by default.
- Rails is more mature : more doc, more help from the web, more stable?, more secure?
- Easier to debug (Grails is known for cumbersome error messages)

My winner: Rails…meanwhile :-)

]]> By: hatim http://www.jtict.com/blog/grails-vs-rails/comment-page-1/#comment-2419 hatim Mon, 13 Jul 2009 00:24:50 +0000 http://www.jtict.com/blog/?p=30#comment-2419 You should also include GoogleAppEngine support, as Grails can be deployed on it You should also include GoogleAppEngine support, as Grails can be deployed on it

]]> By: Beaumont Muni http://www.jtict.com/blog/grails-vs-rails/comment-page-1/#comment-2113 Beaumont Muni Thu, 18 Jun 2009 02:08:35 +0000 http://www.jtict.com/blog/?p=30#comment-2113 Interesting comparison. I use both frameworks ... I am a java developer and use Grails for personal projects but work in a RoR shop where I use Rails all day long. As a developer I am very partial to an approach that is more object orientated. Rails is more data model centric and not so much domain model centric as Grails is in it's approach to the same thing ... so that's why Rails uses models with migration etc ... and Grails uses domain classes. Grails approach tends to flow better with application design using the vertical domain driven model and furthermore I like to stay away from doing SQL if I can. I think Rails 3.0 with datamapper has the right approach along these lines which would help cut down the use of migrations ... which is ugly. Making changes to domain-classes should automatically allow the frame work to change the database table. That's where the strength of the frame work comes into play. GORM in itself is getting to be very powerful. It would be interesting to see where datamapper comes into play in this area. Interesting comparison. I use both frameworks … I am a java developer and use Grails for personal projects but work in a RoR shop where I use Rails all day long. As a developer I am very partial to an approach that is more object orientated. Rails is more data model centric and not so much domain model centric as Grails is in it’s approach to the same thing … so that’s why Rails uses models with migration etc … and Grails uses domain classes. Grails approach tends to flow better with application design using the vertical domain driven model and furthermore I like to stay away from doing SQL if I can. I think Rails 3.0 with datamapper has the right approach along these lines which would help cut down the use of migrations … which is ugly. Making changes to domain-classes should automatically allow the frame work to change the database table. That’s where the strength of the frame work comes into play. GORM in itself is getting to be very powerful. It would be interesting to see where datamapper comes into play in this area.

]]> By: Joshua http://www.jtict.com/blog/grails-vs-rails/comment-page-1/#comment-1973 Joshua Thu, 12 Mar 2009 00:59:28 +0000 http://www.jtict.com/blog/?p=30#comment-1973 I think Django is better than both of them. It has alot of good things out of the box. Plus the best thing that Rails and Grails have :-) I think Django is better than both of them. It has alot of good things out of the box. Plus the best thing that Rails and Grails have :-)

]]> By: Radoslav Stankov http://www.jtict.com/blog/grails-vs-rails/comment-page-1/#comment-1246 Radoslav Stankov Sat, 10 Jan 2009 01:03:32 +0000 http://www.jtict.com/blog/?p=30#comment-1246 I have worked with Rails recently I love Ruby as language. And I think that Rails ActiveRecord is work of art. The one thing I really dislike in Grails is it's name - Groovy on Rails - Grails. As the point from where I see it the whole groovy and grails is created just to have Rails to the Java world. But my opinion is no impartiality. I have worked with Rails recently I love Ruby as language. And I think that Rails ActiveRecord is work of art.
The one thing I really dislike in Grails is it’s name – Groovy on Rails – Grails. As the point from where I see it the whole groovy and grails is created just to have Rails to the Java world.
But my opinion is no impartiality.

]]> By: Juan Salvador http://www.jtict.com/blog/grails-vs-rails/comment-page-1/#comment-1158 Juan Salvador Wed, 31 Dec 2008 21:50:46 +0000 http://www.jtict.com/blog/?p=30#comment-1158 Hi Amigos, I remember, 3 years ago, to Bruce Tate and his "texanian" prediction: "RoR is the Java's killer !!!"... As a Delphi (is it death?) then, Java was a way to survive, and no just that, I really like. From 2005 to now, I have seen Java waking up, with stuff like (the failed) trails, stripes, etc. etc. Trying to read and learn Ruby and Rails, I found out Groovy then Grails and the only thing I regret is the poor support in NetBeans for GaG tools, as Sun seems to be concentrated on JRuby. Grails is for Java Developpers, and in my case for a limited former Delphi developpers. I have a question: Does Ruby have the same set (very big set) of mature tools and frameworks as Java has? I have changed of platform 4 times in the last 20 years (I was a DBase and Clipper programmer 1n 1998), and the main reazon why a had choosen Java is for things like Spring and Hibernate, now the basis of this wonderful framework: grails. I put to work a set of Grails/Groovy applications in 2008, all the time I got the support of tools and frameworks as JFreeChart. maybe Grails is not a grown up as RoR, but its value is based on the Java Platform as it is solid. ALL THE BE>ST IN 2009 Hi Amigos,

I remember, 3 years ago, to Bruce Tate and his “texanian” prediction: “RoR is the Java’s killer !!!”…

As a Delphi (is it death?) then, Java was a way to survive, and no just that, I really like.

From 2005 to now, I have seen Java waking up, with stuff like (the failed) trails, stripes, etc. etc.

Trying to read and learn Ruby and Rails, I found out Groovy then Grails and the only thing I regret is the poor support in NetBeans for GaG tools, as Sun seems to be concentrated on JRuby.

Grails is for Java Developpers, and in my case for a limited former Delphi developpers.

I have a question: Does Ruby have the same set (very big set) of mature tools and frameworks as Java has? I have changed of platform 4 times in the last 20 years (I was a DBase and Clipper programmer 1n 1998), and the main reazon why a had choosen Java is for things like Spring and Hibernate, now the basis of this wonderful framework: grails.

I put to work a set of Grails/Groovy applications in 2008, all the time I got the support of tools and frameworks as JFreeChart. maybe Grails is not a grown up as RoR, but its value is based on the Java Platform as it is solid.

ALL THE BE>ST IN 2009

]]> By: Nadeem Bitar http://www.jtict.com/blog/grails-vs-rails/comment-page-1/#comment-1139 Nadeem Bitar Mon, 29 Dec 2008 22:36:15 +0000 http://www.jtict.com/blog/?p=30#comment-1139 I have used both grails and rails and I strongly prefer rails even though I work in Java and have strong Hibernate and Spring experience. Ruby is simply a more elegant and powerful language than Groovy. The metaprogramming functionality is truly a joy to work with. Rails testing is easier and more comprehensive; grails 1.1 is addressing that but it's still behind. Doing BDD in Ruby/Rails is really nice with frameworks like shoulda. I've tried easyb in groovy but it's not as integrated and polished. The Ruby and Rails communities are bigger and more mature. You can easily find solutions to most problems. Grails using hibernate is not always a benefit. I found myself having to write my mappings in xml many times since the hibernate functionality is not supported yet in grails so I lost all the benefits of grails. Rails view and ajax support is better than grails. Grails does not have anything equivalent to RJS. Rails built in helpers are great. Rails REST support is almost non-existent in grails. Rails routes are extremely powerful and superior to the url mapping in grails. Grails does not support migrations. Grails/Groovy does not have anything equivalent to gem. I've used ivy on my grails project and I know that maven is now supported, but maven is a pain to deal with. I have used both grails and rails and I strongly prefer rails even though I work in Java and have strong Hibernate and Spring experience.

Ruby is simply a more elegant and powerful language than Groovy. The metaprogramming functionality is truly a joy to work with.

Rails testing is easier and more comprehensive; grails 1.1 is addressing that but it’s still behind. Doing BDD in Ruby/Rails is really nice with frameworks like shoulda. I’ve tried easyb in groovy but it’s not as integrated and polished.

The Ruby and Rails communities are bigger and more mature. You can easily find solutions to most problems.

Grails using hibernate is not always a benefit. I found myself having to write my mappings in xml many times since the hibernate functionality is not supported yet in grails so I lost all the benefits of grails.

Rails view and ajax support is better than grails. Grails does not have anything equivalent to RJS. Rails built in helpers are great.

Rails REST support is almost non-existent in grails.

Rails routes are extremely powerful and superior to the url mapping in grails.

Grails does not support migrations.

Grails/Groovy does not have anything equivalent to gem. I’ve used ivy on my grails project and I know that maven is now supported, but maven is a pain to deal with.

]]> By: Pratik http://www.jtict.com/blog/grails-vs-rails/comment-page-1/#comment-1127 Pratik Mon, 29 Dec 2008 13:28:16 +0000 http://www.jtict.com/blog/?p=30#comment-1127 http://guides.rubyonrails.org/ http://guides.rubyonrails.org/

]]> By: Curt Hibbs http://www.jtict.com/blog/grails-vs-rails/comment-page-1/#comment-1122 Curt Hibbs Mon, 29 Dec 2008 04:52:04 +0000 http://www.jtict.com/blog/?p=30#comment-1122 What I think would be more interesting than a checklist comparison, would be an experience report by some who has actually used both frameworks for non-trivial projects. What I think would be more interesting than a checklist comparison, would be an experience report by some who has actually used both frameworks for non-trivial projects.

]]> By: pico http://www.jtict.com/blog/grails-vs-rails/comment-page-1/#comment-1118 pico Sun, 28 Dec 2008 20:21:14 +0000 http://www.jtict.com/blog/?p=30#comment-1118 Sorry, looks like your comments just strip out code instead of escaping it. Just email me if you want me to show you how to create a constructor with default values. Sorry, looks like your comments just strip out code instead of escaping it. Just email me if you want me to show you how to create a constructor with default values.

]]>