CakePHP vs Ruby on Rails. And the battle continues…

When the funny guys at RailsEnvy.com published a video comparing RubyOnRails with PHP, they received a lot of criticisms from the viewers for making an unfair comparison between jets and cars, when they should be comparing jets with jets. The viewers were right. PHP is a language. RubyOnRails is a framework. If they wanted to compare RubyOnRails with something, they should be comparing it with another “framework” instead of a language.

So here is the video commercial I’m talking about (I find these guys to be very entertaining):

Soon after they realized their mistake, they created another video comparing CakePHP with RubyOnRails to be fair to the PHP community. While it’s not really a “comparison”, I still find it so hilarious. Check it out Laughing

LoL. These guys should seriously consider becoming movie actors Tongue out Anyway, it’s true that CakePHP functions the same way RoR works, and I don’t think any Cake Bakers would deny that Cake was initially designed to work like RoR, only in PHP. In fact, there were times when CakePHP used to be nicknamed as “PHP on Rails”. But the way I see it, CakePHP is starting to move on its own way now and becoming more independent the more it grows. Bravo to the CakePHP developers!

CakePHP vs Ruby On Rails. Which is the better framework?

It’s not for me to judge since I never fiddled around much with RubyOnRails before.. at least not as seriously.

What I do know is that both of them follow the MVC design pattern. Both adhere to the “Convention over Configuration” philosophy and Don’t Repeat Yourself (DRY) concept. Both of them also support AJAX. They have an almost identical directory structure. They’re built with testing in mind. They are very OOP-like. They have their own shells for command-line interface stuffs. They both support caching. They support different databases (MySQL, PostgreSQL, etc…). And they’re both released under the MIT license.

The reason why I’m sticking with CakePHP instead of jumping into the RoR bandwagon is because I know I’m already fluent in PHP, so why would I want to learn a new language (Ruby) and a new framework (Rails) when I already have a very Rails-like framework written in PHP? If you strip off “Rails” from Ruby, you’ll realize that Ruby is just another programming language. Sometimes I keep wondering myself why some of those hardcore PHP-ers would migrate completely to RoR and go through the hassles of learning the new syntaxes & built-in functions of Ruby all over again when there’s Cake that does almost entirely the same thing. Even the 37signals guys (the brilliant minds behind RoR) uses PHP in many of their sites. Get real.

To set things straight, RubyOnRails is an awesome framework and I have nothing against it. CakePHP is also an awesome framework. I am no way saying that one is better than the other. They both have their own place and strengths in the web development scene. What I’m saying is unless you want to learn all the programming languages that exists out there, why not just stick with the language you’re currently strong at and use the available framework which works with your favorite language to build the applications of your dream. Save “learning a new language” for your next spare-time hobby. Laughing

Tags: 
Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • BlinkList
  • Ma.gnolia
  • Reddit
  • StumbleUpon


8 Responses to “CakePHP vs Ruby on Rails. And the battle continues…”

  1. Ashrufzz Says:

    Wow..I think I learn more from your post instead of from Wikipedia..keep it up man!!

  2. Tengku Zahasman Says:

    LoL.. thanks for your support ;)

  3. azurt Says:

    The RoR presentor looks cute.. :P

  4. Tengku Zahasman Says:

    … and nerdy at the same time. I’m sure the other guy scores more girls :D

  5. uberdanzik Says:

    Actually, Ruby is a language, which happened to have a supporting structure called ‘rails’ created for it. Most people agree that ruby is the best language in existence for the rails framework structure.

    They should have been comparing cakephp to rubyonrails, and then it would have been fair. But rubyonrails would have blown away cakephp because php is not a very good language to port to rails, its very ackward and has strange quirks. I just learned all about rubyonrails and have written a few programs, and I was horrified to find the conventions used in cakephp.

    Ruby, however is a great language to port to rails, and thats why it was done in the first place. Cake php is merely an impersonation of the real deal, because php got jealous and tried to be cool by jumping on a rails-ish framework. After rubyonrails made headlines, everyone else went frantic looking for a framework to keep up. It’s like trying to put wings on a car and make it fly like a jet - it just isn’t the same.

  6. triqqer Says:

    thanks for the article.

  7. Mr-Yellow Says:

    Yay for fanboys.

    Ruby is a poorly designed language, it is cool how everything is an object, but it’s also completely retarded that everything is an object.

    Anyone who’s ever coded C or ASM will instantly dismiss Ruby as slow based on this design mistake.

    You can’t get around it. It will always be less efficient.

  8. Babak Says:

    Thanks for useful article.

Leave a Comment