Lately, I've been following a group of people on Twitter. Most of them are in the core team of rails. (Should I say the word "geek"?). Anyway these are great people (Mike Gunderloy and others) who invest their time in helping out build the rails framework and now, they're teaching too!

Check out Rails Bridge and the announcements.

RailsBridge Mission is to "create an inclusive and friendly Ruby on Rails community." I admit that while learning rails, I haven't gotten too many responses on IRC but the important thing I guess is to ask yourself first what you really need to know about rails. Some books and resources help but some have "deprecated" code so they're not very useful anymore. If you are smart, do not faithfully follow books.

It may sound unlikely for me to be a rails fan because I'm blogging this using Drupal but soon enough, I'm looking forward to using some open source content management system based on Rails.

Why use Rails? We have CodeIgniter, Zend and CakePHP for people who feel more comfortable with PHP. I'm not so poor with PHP myself as I have been using PHP-based apps since 2003 and that's the same year when I was still seventeen and bored with my subjects in college however it's very difficult to find problems with PHP-based applications. After this post, I'm getting back to trying to trace a problem regarding a site that uses PHP.

Update: I've just seen the RailsConf 2009 video wherein DHH (creator of Rails) talks about the "human wounds" caused by people who didn't have a very good opinion of rails because of their experience. One of those wounds is about a developer who switched backed to using PHP after 2 years on Ruby on Rails. I have actually read the article earlier last year. I just find #6 a fallacy. I've been working on app wherein associations failed in Rails 2.2.2 (a very rare case but I think they've fixed it for the new release). I managed to fix the problem using SQL (shorter code, that is because I still used ActiveRecord's update_attribute and all those conveniences that come with Rails).

Again, there is little difference between rails today and rails five years ago. I see no logical reason in choosing a framework like CakePHP if Rails can be used. If it has a lot to do with doubts on scaling, then find out what how to scale app using Rails.

comments powered byDisqus

Hello! I am Kat. I've been a developer for several years. When I'm not sitting down, reading and working for long hours, I am traveling to some place of interest.
If you want to reach out, you can send me an email or add me up on Google Plus.