Today I decided to do something different, something I’ve been dying to do since before coming across CakePHP: give Rails a proper try. Like many other PHP developers out there, when Ruby on Rails came out I felt damn jealous and terribly tempted to learn Ruby only to start using such an amazing web development framework. At the time I actually even started reading various tutorials about it, and I was literally amazed at how RoR revolutioned the way of developing web applications.
One of the main problems which made me – sadly – abandon Rails was Ruby itself: personally I’ve never seen a programming language with a cleaner and more elegant syntax, but also – at least at the time – there weren’t many hosts supporting it. LuckilyI found CakePHP quickly after that…
Now however, more and more hosting companies boast full Rails support, and so when recently I had to move to a new host, I made sure it was Rails-friendly, just in case I wanted to give Rails another try, someday.
Oh well, the temptation was so strong that today, only a two days after switching to my new host, I felt I had to try it, I had to taste something different than the usual Cake.
I decided to (re-)read and follow the OnLamp tutorial about RoR, step by step, once again. I quickly typed
rails cookbook from my shell and voilá, rails silently creates the skeleton of my application:
That’s familiar: it’s very similar to what CakePHP’s directory structure used to look like. Now Cake evolved and adopted its own schema, which – I must say – seems more functional than RoR’s, at least at a first glance:
Cake felt the necessity to divide what you can mess with (
vendors/) from what you’d better not touch (
cake/). Rails just left everything on the same level.
After creating my database and the necessary tables I have to edit
config/database.yml, which corresponds to Cake’s
app/config/database.php. Then things start to become a bit different from Cake, as Rails offers some very handy built in scripts which can be used to automatically create your application’s files, i.e. executing
ruby script/generate controller Recipe creates the controller and other bits:
exists app/controllers/ exists app/helpers/ create app/views/recipe exists test/functional/ create app/controllers/recipe_controller.rb create test/functional/recipe_controller_test.rb create app/helpers/recipe_helper.rb
And so on. Anyhow… I followed the tutorial and yes, it was a nice read. CakePHP borrowed a lot from Rails but not everything. Inevitably Ruby’s syntax is less verbose and looks very very clean:
<% highlight :ruby do %>
class RecipeController < ApplicationController
@recipes = Recipe.find_all
recipe = Recipe.find(params[“id”])
@categories = Category.find_all
<% end %>
While CakePHP’s, simply because it uses PHP and not Ruby, looks less pretty:
<% highlight :php do %>
class RecipesController extends AppController
$this→set(‘recipe’, $this→Recipe→find(“id = $id”));
<% end %>
CakePHP Development Team did a great job translating some of Rails functionalities into PHP, and the while CakePHP’s syntax is much cleaner if compared to PHP’s standard spaghetti-code approach, Ruby just looks much more clear, sorry. Imagine a world without funny unnecessary brackets, pointless semicolons and where everything just looks better: that’s Ruby.
Sigh. Now I do understand why Rails was built in Ruby and not in PHP: simply because a PHP’s Rails would have been outscored by its “Ruby port”!
One thing I liked about Rails which has not been ported in Cake (yet) is a somehow smarter way of scaffolding. While the Ruby code above actually works, the CakePHP’s edit method doesn’t, or better, it does but not as expected: when you remove
var $scaffold the scaffold is just plain gone, and you have to code everything yourself, while in Ruby you can leave the scaffold and then develop methods one by one, and still be able to use scaffolded methods if you didn’t define the custom ones.
The other thing I noticed about RoR is that it definitely handles errors better! This is probably another language issue. I basically forgot to set a category for the recipes, and when executing my custom list of recipes I got a very, very well structured error page showing something like:
<% highlight :ruby do %>
NoMethodError in Recipe#index
Showing app/views/recipe/index.rhtml where line #18 raised:
You have a nil object when you didn’t expect it!
The error occured while evaluating nil.name
Extracted source (around line #18):
15: <% @recipes.each do |recipe| >
<= link_to recipe.title, :action => “show”, :id => recipe.id >
<= recipe.category.name >
<= recipe.date >
21: < end >
< end %>
I took a screenshot of the page, because it was too nice: check it out. This error page really tells you what’s wrong, and even prints the lines of code around the error! It also lets the developer check the full backtrace and every sort of information… Can we have this in CakePHP please? I actually started to develop something like this, but seemed quite hard to do in PHP.