<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.5" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Why I Prefer Ruby on Rails over CakePHP</title>
	<link>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html</link>
	<description>Web Entrepreneur</description>
	<pubDate>Thu, 24 Jul 2008 07:15:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Baz L</title>
		<link>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-62056</link>
		<dc:creator>Baz L</dc:creator>
		<pubDate>Mon, 07 Apr 2008 13:56:09 +0000</pubDate>
		<guid>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-62056</guid>
		<description>One thing I'm confused about...Automatically querying data in the view? Unless I'm missing something, I wasn't able to get this to work. Always got an existence error, unless I modify my find in the controller...

Please enlighten me.</description>
		<content:encoded><![CDATA[<p>One thing I&#8217;m confused about&#8230;Automatically querying data in the view? Unless I&#8217;m missing something, I wasn&#8217;t able to get this to work. Always got an existence error, unless I modify my find in the controller&#8230;</p>
<p>Please enlighten me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mbavio</title>
		<link>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-61094</link>
		<dc:creator>mbavio</dc:creator>
		<pubDate>Thu, 03 Apr 2008 13:50:38 +0000</pubDate>
		<guid>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-61094</guid>
		<description>Better late than never...

http://bakery.cakephp.org/articles/view/bindable-behavior-control-your-model-bindings

Read that article, then write tihs post again.

Cheers,
mbavio</description>
		<content:encoded><![CDATA[<p>Better late than never&#8230;</p>
<p><a href="http://bakery.cakephp.org/articles/view/bindable-behavior-control-your-model-bindings" rel="nofollow">http://bakery.cakephp.org/articles/view/bindable-behavior-control-your-model-bindings</a></p>
<p>Read that article, then write tihs post again.</p>
<p>Cheers,<br />
mbavio</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimmy'z</title>
		<link>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-48152</link>
		<dc:creator>Jimmy'z</dc:creator>
		<pubDate>Fri, 15 Feb 2008 15:52:39 +0000</pubDate>
		<guid>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-48152</guid>
		<description>I've looked into the Zend Framework, but I haven't used it on a real project.

Cake and Rails both follow a principle of "Convention over Configuration" which makes them a bit less flexible, but very easy to get up and running and to maintain. Zend Framework requires a lot of configuration, so you will spend a lot of up-front time getting your configurations right rather than building your core software.

Some people see Cake and Rails as a bloated framework, but I think their benefits far outweigh the costs of a large framework. Rails has cut down the bloat quite a bit in v2.0 by pushing a lot of the functionality into plug-ins. However the plug-in structure is really easy to maintain.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve looked into the Zend Framework, but I haven&#8217;t used it on a real project.</p>
<p>Cake and Rails both follow a principle of &#8220;Convention over Configuration&#8221; which makes them a bit less flexible, but very easy to get up and running and to maintain. Zend Framework requires a lot of configuration, so you will spend a lot of up-front time getting your configurations right rather than building your core software.</p>
<p>Some people see Cake and Rails as a bloated framework, but I think their benefits far outweigh the costs of a large framework. Rails has cut down the bloat quite a bit in v2.0 by pushing a lot of the functionality into plug-ins. However the plug-in structure is really easy to maintain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gil</title>
		<link>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-47888</link>
		<dc:creator>Gil</dc:creator>
		<pubDate>Thu, 14 Feb 2008 17:41:14 +0000</pubDate>
		<guid>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-47888</guid>
		<description>Great post dude. I have yet to jump into either Cake or Rails, and my main project is a combination of the two, but I'll keep this in mind if I ever start looking into Cake.

Did you try the Zend Framework at all?</description>
		<content:encoded><![CDATA[<p>Great post dude. I have yet to jump into either Cake or Rails, and my main project is a combination of the two, but I&#8217;ll keep this in mind if I ever start looking into Cake.</p>
<p>Did you try the Zend Framework at all?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimmy'z</title>
		<link>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-38562</link>
		<dc:creator>Jimmy'z</dc:creator>
		<pubDate>Sat, 05 Jan 2008 15:48:10 +0000</pubDate>
		<guid>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-38562</guid>
		<description>While it's true that PHP has a lot more code and classes available, I've had a lot easier time finding quality libraries in the Ruby community.

Also, Ruby's 'gem' library repository makes it a joy to install and use new libraries. I don't find the same amount of quality libraries available in PEAR.

Because Ruby is and always has been a fully Object Oriented language, all of the code available is object oriented.

The same is not true in the PHP community. There are tons of snippets that are just plain old procedural code that is hard to reuse or extend. This leads to a lot of sifting through a lot of junk code when looking for an existing library.

Also, there are a ton of good Rails plug-ins that are super easy to apply to your application. Plug-ins work especially well in Ruby because you can re-open classes to inject functionality, and mix in modules to gain functionality. I believe the Rails community is larger than any community gathered around a single PHP framework. It is really nice to be able to find lots of plug-ins specific to the framework that I am using. I rarely have a problem finding a good plug-in for accomplishing common web-related tasks.

I'm not saying that Rails and Ruby are the only way to go. PHP does some things very nicely and has some good advantages.</description>
		<content:encoded><![CDATA[<p>While it&#8217;s true that PHP has a lot more code and classes available, I&#8217;ve had a lot easier time finding quality libraries in the Ruby community.</p>
<p>Also, Ruby&#8217;s &#8216;gem&#8217; library repository makes it a joy to install and use new libraries. I don&#8217;t find the same amount of quality libraries available in PEAR.</p>
<p>Because Ruby is and always has been a fully Object Oriented language, all of the code available is object oriented.</p>
<p>The same is not true in the PHP community. There are tons of snippets that are just plain old procedural code that is hard to reuse or extend. This leads to a lot of sifting through a lot of junk code when looking for an existing library.</p>
<p>Also, there are a ton of good Rails plug-ins that are super easy to apply to your application. Plug-ins work especially well in Ruby because you can re-open classes to inject functionality, and mix in modules to gain functionality. I believe the Rails community is larger than any community gathered around a single PHP framework. It is really nice to be able to find lots of plug-ins specific to the framework that I am using. I rarely have a problem finding a good plug-in for accomplishing common web-related tasks.</p>
<p>I&#8217;m not saying that Rails and Ruby are the only way to go. PHP does some things very nicely and has some good advantages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allan Jensen</title>
		<link>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-38530</link>
		<dc:creator>Allan Jensen</dc:creator>
		<pubDate>Sat, 05 Jan 2008 13:00:56 +0000</pubDate>
		<guid>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-38530</guid>
		<description>I would say that it's not only a matter of how well Ruby on Rails works compared to CakePHP in relation to MVC, but also the overall picture of the two languages.

PHP is very mature and there are tons of code and classes and stuff available for doing all kinds of things, so you don't have to do it yourself.

RoR is still new, and have a smaller community, and I would guess that code availability is far from reaching the level that as of PHP. This means that you'll have to do a lot of these things yourself - which of course means spending a lot more time programming. That's why I'm skeptical with switching to PHP.

And besides, even having programmed a huge website over 5 years in PHP (and still developing), I haven't found PHP unable to manage the complexity that the website requires - on the contrary, I love PHP/MySQL and it works wonder for us!</description>
		<content:encoded><![CDATA[<p>I would say that it&#8217;s not only a matter of how well Ruby on Rails works compared to CakePHP in relation to MVC, but also the overall picture of the two languages.</p>
<p>PHP is very mature and there are tons of code and classes and stuff available for doing all kinds of things, so you don&#8217;t have to do it yourself.</p>
<p>RoR is still new, and have a smaller community, and I would guess that code availability is far from reaching the level that as of PHP. This means that you&#8217;ll have to do a lot of these things yourself - which of course means spending a lot more time programming. That&#8217;s why I&#8217;m skeptical with switching to PHP.</p>
<p>And besides, even having programmed a huge website over 5 years in PHP (and still developing), I haven&#8217;t found PHP unable to manage the complexity that the website requires - on the contrary, I love PHP/MySQL and it works wonder for us!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimmy'z</title>
		<link>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-29509</link>
		<dc:creator>Jimmy'z</dc:creator>
		<pubDate>Mon, 12 Nov 2007 18:45:43 +0000</pubDate>
		<guid>http://jimmyzimmerman.com/blog/2007/05/why-i-prefer-ruby-on-rails-over-cakephp.html#comment-29509</guid>
		<description>I hear Cake's model is continuing to receive improvements.

Having to unbind models is extra work that I'd prefer not to have to worry about, but at least it's there so that you're not pulling down the entire database to get to a specific piece of data.</description>
		<content:encoded><![CDATA[<p>I hear Cake&#8217;s model is continuing to receive improvements.</p>
<p>Having to unbind models is extra work that I&#8217;d prefer not to have to worry about, but at least it&#8217;s there so that you&#8217;re not pulling down the entire database to get to a specific piece of data.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
