<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Comparing Ruby on Rails to Grails</title>
	<atom:link href="http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/feed" rel="self" type="application/rss+xml" />
	<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails</link>
	<description>Thoughts on poker, programming and other stuff.</description>
	<lastBuildDate>Thu, 11 Mar 2010 18:00:51 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Thesis papers</title>
		<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/comment-page-1#comment-18741</link>
		<dc:creator>Thesis papers</dc:creator>
		<pubDate>Thu, 28 Jan 2010 12:08:49 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/03/21/comparing-ruby-on-rails-to-grails/#comment-18741</guid>
		<description>Hi,
A fantastic read, it is very literate and informative. Many thanks….what theme is this you are using also.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
A fantastic read, it is very literate and informative. Many thanks….what theme is this you are using also.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pragmatic Chris &#187; Blog Archive &#187; Grails is not Rails</title>
		<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/comment-page-1#comment-4312</link>
		<dc:creator>Pragmatic Chris &#187; Blog Archive &#187; Grails is not Rails</dc:creator>
		<pubDate>Sat, 12 Jan 2008 20:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/03/21/comparing-ruby-on-rails-to-grails/#comment-4312</guid>
		<description>[...] article gives a really good summary of the differences in the design approach between Rails and Grails:  [...]</description>
		<content:encoded><![CDATA[<p>[...] article gives a really good summary of the differences in the design approach between Rails and Grails:  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Hosting Reviews, Web Site Hosting</title>
		<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/comment-page-1#comment-2867</link>
		<dc:creator>Web Hosting Reviews, Web Site Hosting</dc:creator>
		<pubDate>Sat, 03 Nov 2007 11:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/03/21/comparing-ruby-on-rails-to-grails/#comment-2867</guid>
		<description>&lt;strong&gt;Web Hosting Reviews, Web Site Hosting...&lt;/strong&gt;

I couldn&#039;t understand some parts of this article, but it sounds interesting...</description>
		<content:encoded><![CDATA[<p><strong>Web Hosting Reviews, Web Site Hosting&#8230;</strong></p>
<p>I couldn&#8217;t understand some parts of this article, but it sounds interesting&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Bull</title>
		<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/comment-page-1#comment-1135</link>
		<dc:creator>The Bull</dc:creator>
		<pubDate>Thu, 26 Apr 2007 16:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/03/21/comparing-ruby-on-rails-to-grails/#comment-1135</guid>
		<description>Now now dantebronto be nice... I believe I&#039;ve mentioned before that RoR will beat Java in the &#039;public&#039; app space, much like PHP does today. However, in the enterprise market it will take far longer for Ruby to penetrate and Java will be king for quite some time.

As for the &#039;beastly JVM&#039;, well JRuby is moving along quite nicely and almost has complete support for Ruby on Rails applications. Not to mention that Graeme has already shown that early testing of Grails outperforms Ruby on Rails.

I&#039;m aware of eapps BTW. I just looked and they have some good stuff since I last saw them.</description>
		<content:encoded><![CDATA[<p>Now now dantebronto be nice&#8230; I believe I&#8217;ve mentioned before that RoR will beat Java in the &#8216;public&#8217; app space, much like PHP does today. However, in the enterprise market it will take far longer for Ruby to penetrate and Java will be king for quite some time.</p>
<p>As for the &#8216;beastly JVM&#8217;, well JRuby is moving along quite nicely and almost has complete support for Ruby on Rails applications. Not to mention that Graeme has already shown that early testing of Grails outperforms Ruby on Rails.</p>
<p>I&#8217;m aware of eapps BTW. I just looked and they have some good stuff since I last saw them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dantebronto</title>
		<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/comment-page-1#comment-1127</link>
		<dc:creator>dantebronto</dc:creator>
		<pubDate>Thu, 26 Apr 2007 04:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/03/21/comparing-ruby-on-rails-to-grails/#comment-1127</guid>
		<description>I am a Ruby-biased system admin for a web hosting company that specializes in Java. &quot;Groovy on Grails&quot;, besides sounding like a bad joke, is doomed against Rails in the long run. Ruby is potentially a lot better suited for small applications, especially in hosting environments with limited memory. Trying to tack Rails-like functionality on top of the beastly JVM is a recipe for frustration IMO.

Check out http://eapps.com for both Java and Rails done right and with GENIUS support. That way you can still host the last of your Java apps whilst you learn RoR :-)</description>
		<content:encoded><![CDATA[<p>I am a Ruby-biased system admin for a web hosting company that specializes in Java. &#8220;Groovy on Grails&#8221;, besides sounding like a bad joke, is doomed against Rails in the long run. Ruby is potentially a lot better suited for small applications, especially in hosting environments with limited memory. Trying to tack Rails-like functionality on top of the beastly JVM is a recipe for frustration IMO.</p>
<p>Check out <a href="http://eapps.com" rel="nofollow">http://eapps.com</a> for both Java and Rails done right and with GENIUS support. That way you can still host the last of your Java apps whilst you learn RoR <img src='http://thebull.macsimumweb.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-03-23 &#124; Urubatan`s Weblog</title>
		<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/comment-page-1#comment-898</link>
		<dc:creator>links for 2007-03-23 &#124; Urubatan`s Weblog</dc:creator>
		<pubDate>Fri, 23 Mar 2007 05:37:33 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/03/21/comparing-ruby-on-rails-to-grails/#comment-898</guid>
		<description>[...] Comparing Ruby on Rails to Grails » Thinking Outloud (tags: java) [...]</description>
		<content:encoded><![CDATA[<p>[...] Comparing Ruby on Rails to Grails » Thinking Outloud (tags: java) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Bull</title>
		<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/comment-page-1#comment-897</link>
		<dc:creator>The Bull</dc:creator>
		<pubDate>Fri, 23 Mar 2007 04:51:29 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/03/21/comparing-ruby-on-rails-to-grails/#comment-897</guid>
		<description>You are correct Daiji, Ruby itself has been around for quite a while although it hasn&#039;t gotten mainstream acceptance until Ruby on Rails made its big splash on the scene as you mentioned. I should have made that point as well.

I think initially smaller companies will lean towards RoR while the bigger ones go towards Grails if for no other reason that Grails is Java based and thus there is a wider developer base (for the time being) which is a consideration when it comes to staffing. With regards to the bigger companies, it will be the developers themselves going towards Grails more than a &#039;company&#039; decision. I&#039;ve certainly been one of the developers before that started using a new framework for an application for whatever reason (RAD, curiosity, whatever) and the company didn&#039;t care as long as it ran on their chosen platform, i.e. a JavaEE server and it was documented. Smaller companies might be more inclined to have specific reasons for one over the other, especially if that company is basing their product on the software being written (again I point to 37signals). 

There is enough buzz and interest in Rails however that I think the performance side of it will increase at a faster pace than Java&#039;s did back in the day.</description>
		<content:encoded><![CDATA[<p>You are correct Daiji, Ruby itself has been around for quite a while although it hasn&#8217;t gotten mainstream acceptance until Ruby on Rails made its big splash on the scene as you mentioned. I should have made that point as well.</p>
<p>I think initially smaller companies will lean towards RoR while the bigger ones go towards Grails if for no other reason that Grails is Java based and thus there is a wider developer base (for the time being) which is a consideration when it comes to staffing. With regards to the bigger companies, it will be the developers themselves going towards Grails more than a &#8216;company&#8217; decision. I&#8217;ve certainly been one of the developers before that started using a new framework for an application for whatever reason (RAD, curiosity, whatever) and the company didn&#8217;t care as long as it ran on their chosen platform, i.e. a JavaEE server and it was documented. Smaller companies might be more inclined to have specific reasons for one over the other, especially if that company is basing their product on the software being written (again I point to 37signals). </p>
<p>There is enough buzz and interest in Rails however that I think the performance side of it will increase at a faster pace than Java&#8217;s did back in the day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daiji</title>
		<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/comment-page-1#comment-896</link>
		<dc:creator>Daiji</dc:creator>
		<pubDate>Fri, 23 Mar 2007 04:26:55 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/03/21/comparing-ruby-on-rails-to-grails/#comment-896</guid>
		<description>I believe your rationale for deciding to exclude performance is fundamentally flawed.

Re: &quot;As for the performance I intentionally left that out because I thought I would get more backlash about it still being new, Java having a 10+ year head start, etc. etc.&quot;

I would like to note that this is wrong.  Technically, Ruby is actually only a few years younger than Java&#039;s initial revs (and about the same in terms of publicly-released years), and certainly far older than Groovy; and that Rails is also certainly older than Grails.

I will admit though, that whereas the JVM has had popular exposure since a few years after it was publicly released, Ruby appears to only have had a popular presence since the appearance of Rails (and only recently received a VM).  Furthermore, Hibernate has had more time than ActiveRecord to mature.  

But companies don&#039;t choose a development platform on the hopes that performance will improve, but that the performance is sufficient and that the development effort is reasonable.  It seems to me that Rails may be a more mature framework and will be appealing to shops where performance is not a top priority, but that Grails has the performance advantage, and can work with pre-existing Java web development efforts, and is built on top of very mature pre-existing Java frameworks, and therefore is more appropriate/comfortable for development when performance is more important, but development speed cannot be sacrificed.

I&#039;d personally like to see the RoR developers respond to Graeme&#039;s performance comparison.  If that means that they run the test using JRuby, a better CGI, or some newer version of a RubyVM, so be it.  At this point, I believe that the ball is in their court to prove that they can match Grails performance.</description>
		<content:encoded><![CDATA[<p>I believe your rationale for deciding to exclude performance is fundamentally flawed.</p>
<p>Re: &#8220;As for the performance I intentionally left that out because I thought I would get more backlash about it still being new, Java having a 10+ year head start, etc. etc.&#8221;</p>
<p>I would like to note that this is wrong.  Technically, Ruby is actually only a few years younger than Java&#8217;s initial revs (and about the same in terms of publicly-released years), and certainly far older than Groovy; and that Rails is also certainly older than Grails.</p>
<p>I will admit though, that whereas the JVM has had popular exposure since a few years after it was publicly released, Ruby appears to only have had a popular presence since the appearance of Rails (and only recently received a VM).  Furthermore, Hibernate has had more time than ActiveRecord to mature.  </p>
<p>But companies don&#8217;t choose a development platform on the hopes that performance will improve, but that the performance is sufficient and that the development effort is reasonable.  It seems to me that Rails may be a more mature framework and will be appealing to shops where performance is not a top priority, but that Grails has the performance advantage, and can work with pre-existing Java web development efforts, and is built on top of very mature pre-existing Java frameworks, and therefore is more appropriate/comfortable for development when performance is more important, but development speed cannot be sacrificed.</p>
<p>I&#8217;d personally like to see the RoR developers respond to Graeme&#8217;s performance comparison.  If that means that they run the test using JRuby, a better CGI, or some newer version of a RubyVM, so be it.  At this point, I believe that the ball is in their court to prove that they can match Grails performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Bull</title>
		<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/comment-page-1#comment-895</link>
		<dc:creator>The Bull</dc:creator>
		<pubDate>Fri, 23 Mar 2007 02:45:04 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/03/21/comparing-ruby-on-rails-to-grails/#comment-895</guid>
		<description>Jason: Oh I understand enough of Hibernate having used it several times and while it is true that I do not like it overall, it definitely has its place. For what it does do it does do well, so I don&#039;t knock it by saying &quot;it sucks&quot;. As an pure ORM it works great if you don&#039;t mind living with the db schema constraints. Given that I have also built two ORMs myself I understand what it takes to do them. No they aren&#039;t easy, no Hibernate doesn&#039;t suck. It certainly has whipped CocoBase, Toplink, EJB entity beans, et al in adoption as an ORM tool. Props to the Hibernate team for that. I just happen to build applications where Hibernate either didn&#039;t perform or was far too constraining.

If by &quot;Grails is going to be for serious development and serious projects&quot; you mean the &#039;enterprise&#039; market I agree UNLESS JRuby really takes off and supports RoR really well. To call the current RoR applications out there not serious (such as the apps developed by 37Signals) isn&#039;t fair though.

autocrat: Fair enough! I did see the roadmap about the middlegen integration and I honestly forgot to mention it, so you are correct there. 

As for the performance I intentionally left that out because I thought I would get more backlash about it still being new, Java having a 10+ year head start, etc. etc. There was a time when Java wasn&#039;t all that speedy and it took a few years before the JVMs came along that made it really shine. So to be fair Grails does have the advantage because it runs on those VMs and I&#039;m sure Mongrel, etc. will catch up. Then again, perhaps we could be running Ruby on the VM and then we would have some real benchmarks!

Good debate gentlemen, thanks for the comments!</description>
		<content:encoded><![CDATA[<p>Jason: Oh I understand enough of Hibernate having used it several times and while it is true that I do not like it overall, it definitely has its place. For what it does do it does do well, so I don&#8217;t knock it by saying &#8220;it sucks&#8221;. As an pure ORM it works great if you don&#8217;t mind living with the db schema constraints. Given that I have also built two ORMs myself I understand what it takes to do them. No they aren&#8217;t easy, no Hibernate doesn&#8217;t suck. It certainly has whipped CocoBase, Toplink, EJB entity beans, et al in adoption as an ORM tool. Props to the Hibernate team for that. I just happen to build applications where Hibernate either didn&#8217;t perform or was far too constraining.</p>
<p>If by &#8220;Grails is going to be for serious development and serious projects&#8221; you mean the &#8216;enterprise&#8217; market I agree UNLESS JRuby really takes off and supports RoR really well. To call the current RoR applications out there not serious (such as the apps developed by 37Signals) isn&#8217;t fair though.</p>
<p>autocrat: Fair enough! I did see the roadmap about the middlegen integration and I honestly forgot to mention it, so you are correct there. </p>
<p>As for the performance I intentionally left that out because I thought I would get more backlash about it still being new, Java having a 10+ year head start, etc. etc. There was a time when Java wasn&#8217;t all that speedy and it took a few years before the JVMs came along that made it really shine. So to be fair Grails does have the advantage because it runs on those VMs and I&#8217;m sure Mongrel, etc. will catch up. Then again, perhaps we could be running Ruby on the VM and then we would have some real benchmarks!</p>
<p>Good debate gentlemen, thanks for the comments!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://thebull.macsimumweb.com/comparing-ruby-on-rails-to-grails/comment-page-1#comment-894</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Fri, 23 Mar 2007 02:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/03/21/comparing-ruby-on-rails-to-grails/#comment-894</guid>
		<description>No offense, but this is just sad. I know you tried to compare, but you did nothing more than state opinion on each one. And you don&#039;t even have your facts straight! You simply do not understand the underlying technologies of Grails (hibernate, for one) to make any sensible comment. 

Yes, RoR might well be the next PHP. Fine..take the market. Grails is going to be for serious development and serious projects.</description>
		<content:encoded><![CDATA[<p>No offense, but this is just sad. I know you tried to compare, but you did nothing more than state opinion on each one. And you don&#8217;t even have your facts straight! You simply do not understand the underlying technologies of Grails (hibernate, for one) to make any sensible comment. </p>
<p>Yes, RoR might well be the next PHP. Fine..take the market. Grails is going to be for serious development and serious projects.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
