<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Sproutly - Latest Comments in CakePHP vs. Ruby on Rails</title><link>http://sproutly.disqus.com/</link><description></description><atom:link href="https://sproutly.disqus.com/cakephp_vs_ruby_on_rails/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 20 Feb 2010 08:05:44 -0000</lastBuildDate><item><title>Re: CakePHP vs. Ruby on Rails</title><link>http://www.sproutly.com/2008/04/26/cakephp-vs-ruby-on-rails/#comment-35622091</link><description>&lt;p&gt;Ruby has been debated to be slow.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Life in Africa</dc:creator><pubDate>Sat, 20 Feb 2010 08:05:44 -0000</pubDate></item><item><title>Re: CakePHP vs. Ruby on Rails</title><link>http://www.sproutly.com/2008/04/26/cakephp-vs-ruby-on-rails/#comment-14560833</link><description>&lt;p&gt;What did you decide on? I'm making this decision now, and I have only basic knowledge of PHP.&lt;/p&gt;&lt;p&gt;My thoughts:&lt;br&gt;*I know a little PHP, and so does the guy I intend to work with.&lt;br&gt;*My application has some scripting involved, so it might be better to use Ruby throughout than PHP for the site and Python for the scripting.&lt;br&gt;*I have worked in a team project on designing a web site in Django, and I know Python very well from work. However, I didn't do much with the higher-level Django stuff.&lt;br&gt;*I'd like to have an impressive resume; right now I could say that I know PHP (though not well) and Python, so maybe Ruby would be a good addition. Or maybe solid PHP knowledge would be better.&lt;br&gt;*My fiancee's name is Ruby ;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">airandfingers</dc:creator><pubDate>Mon, 10 Aug 2009 06:02:48 -0000</pubDate></item><item><title>Re: CakePHP vs. Ruby on Rails</title><link>http://www.sproutly.com/2008/04/26/cakephp-vs-ruby-on-rails/#comment-384948</link><description>&lt;p&gt;Koder, I call FUD.&lt;/p&gt;&lt;p&gt;See &lt;a href="http://modrails.com" rel="nofollow noopener" target="_blank" title="http://modrails.com"&gt;http://modrails.com&lt;/a&gt; for super-easy Rails deployment.&lt;/p&gt;&lt;p&gt;And scaling (in a web-sense) has absolutely nothing to do with your programming language.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eelco</dc:creator><pubDate>Sun, 27 Apr 2008 07:45:22 -0000</pubDate></item><item><title>Re: CakePHP vs. Ruby on Rails</title><link>http://www.sproutly.com/2008/04/26/cakephp-vs-ruby-on-rails/#comment-384853</link><description>&lt;p&gt;Ok, this is the real deal.&lt;/p&gt;&lt;p&gt;20 million sites are using PHP. PHP is the only specialized dynamic scripting language for the Web. Ruby and Perl are old languages and they are way to generic. Ruby is kind of fun, but it is not mature enough. It doesn't scale, and this is due to its execution model, see, Ruby doesn't have mod_php, and it will never do, because it's a generic scripting language. PHP is a member of the LAMP family, yes, the most popular opens-source operating system, Web server and database administration server. Big companies such as IBM, Yahoo, Fiat, Sony and others are using PHP. Large-scale applications are powered by PHP, such as Wikipedia, Facebook and, do you need more?&lt;/p&gt;&lt;p&gt;Perl is from the 80's and Ruby from the 90's. My friend, wake up, PHP was the last dynamic language to emerge and the one that took over. PHP is not only the present, but also the future.&lt;/p&gt;&lt;p&gt;You need a good framework, an enterprise MVC framework? That is secure, scales, and performs well? Use the Zend Framework. &lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Koder</dc:creator><pubDate>Sun, 27 Apr 2008 05:35:55 -0000</pubDate></item><item><title>Re: CakePHP vs. Ruby on Rails</title><link>http://www.sproutly.com/2008/04/26/cakephp-vs-ruby-on-rails/#comment-384840</link><description>&lt;p&gt;I can confirm what Luigi is saying. I was checking the capabilities of rails, but had to develop an application for a shared host. I chode CakePHP and many features are similar to those of RubyOnRails, but the language… Ruby is so much more beautiful and supports the developer. Most other languages I know do the opposite ;)&lt;br&gt;After this project I never did any other PHP project (only small single pages). And I haven't regret it so far&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maximilian Schulz</dc:creator><pubDate>Sun, 27 Apr 2008 05:11:00 -0000</pubDate></item><item><title>Re: CakePHP vs. Ruby on Rails</title><link>http://www.sproutly.com/2008/04/26/cakephp-vs-ruby-on-rails/#comment-384730</link><description>&lt;p&gt;One of the major benefits of CakePHP is how incredibly simple it is to deploy.  It takes a few minutes.&lt;/p&gt;&lt;p&gt;Ruby on Rails can take a few hours if things don't go smoothly and it requires quite a bit of configuration, plus you may need to switch hosting providers to even get it working.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben Bleikamp</dc:creator><pubDate>Sun, 27 Apr 2008 02:36:16 -0000</pubDate></item><item><title>Re: CakePHP vs. Ruby on Rails</title><link>http://www.sproutly.com/2008/04/26/cakephp-vs-ruby-on-rails/#comment-384575</link><description>&lt;p&gt;My favourite at the moment is Pylons. You can take what you need and leave the rest. It's more a collection of different subprojects integrated under one banner. And you can pick and choose what suits you and leave the rest. I like that.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cris</dc:creator><pubDate>Sun, 27 Apr 2008 00:15:53 -0000</pubDate></item><item><title>Re: CakePHP vs. Ruby on Rails</title><link>http://www.sproutly.com/2008/04/26/cakephp-vs-ruby-on-rails/#comment-384543</link><description>&lt;p&gt;I was a PHP developer in 2005, then heard about Ruby on Rails and found CakePHP and thought that it was a good mix between a Rails-inspired MVC framework and PHP. CakePHP is great, and I think everyone who works in PHP should use it.&lt;/p&gt;&lt;p&gt;But late in 2006 I bit the bullet and learned Ruby + Rails, and I've never looked back. Ruby is a world better than PHP. The CakePHP guys deserve a lot of credit, but Rails (and now other projects like Merb) are simply a step above, and a lot of it has to do with how much better Ruby is.&lt;/p&gt;&lt;p&gt;Just my 2 cents...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Luigi Montanez</dc:creator><pubDate>Sat, 26 Apr 2008 23:57:27 -0000</pubDate></item></channel></rss>