ruby on rails

Do We Not Understand What Bias Means?

Somehow I don’t think most people understood what my bias comparison of CakePHP vs Ruby on rails meant. The last few visitors to comments seem to have been Rails fans. One of them seems to think that I shouldn’t touch Ruby on Rails with a ten foot pole and should stick with CakePHP. He doesn’t want someone like me in their community. The other comment, I get the opposite vibe from.

CakePHP vs. Ruby On Rails – A Very Bias Look at Why I Choose CakePHP

First of let me state that this post is very bias towards CakePHP. Truth be told, I haven’t even installed or used Ruby on Rails. The closest I’ve come is looking at various code snippets I’ve found around. With that said, you may want to stop reading now.

These arguments are not based on hard facts, since I haven’t done much research on the matter. A lot of them come from a post at Clickable Bliss discussing the PHP vs. Ruby On Rails Issue.

  1. Steep Learning Curve - Laziness

One thing I really hate is learning stuff. It is especially bothersome when you're trying to crank out a project or web application in a limited amount of time.

With CakePHP I'm required to learn about the **MVC style of development** as well as CakePHP **conventions**.

With Ruby on Rails, I would have to learn MVC, Ruby on Rails conventions and I would have to s**tart from scratch with the Ruby programming language** as well.