Why Ruby on Rails?

I have developed Web sites in technologies such as: Microsoft ASP, PHP. However, I began to learn Ruby on Rails in 2008, and now I am partial to it. I heard how good it is from a couple associates, and decided I would do a project in Ruby on Rails. And now that I have done some work with it, I can really see the strengths of Ruby On Rails. Thanks to Pat and Sean for insisting that I take part in the fun of Web development in Ruby.

The plus points to Ruby on Rails lie in it's ability to allow the developer to put his ideas into reality easier with the well organized framework of Rails; also allowing the developer to consider Web 2.0 principles and realize them quicker and easier.

Here is a good diagram that explains how Rails is organized:

Above picture taken from Agile Web Development with Rails, Second edition by Dave Thomas and David Heinemeier Hansson.

The best way to understand why and how Ruby On Rails architecture is choice, is do a Web site project in Rails. To a developer, the main attraction is that Ruby on Rails favors convention over configuration; so less configuring, and as a result more done with less typing and work. To a Web site owner, the benefit is friendly paths in the address bar, a good frame to build and expand your Web site—longevity, and search-engine optimization friendly as well.

I have gone through some of the pains and difficulties inherent to learning anything new, so I understand if anyone is going through difficulties with Rails, so feel free to ask for help.

There is much more to be said about Ruby on Rails, so I suggest going to RubyonRails.org and getting started with your first project and getting connected with the online community. Also get hooked up with a Ruby on Rails hosting service, it's best to locate somebody in your area so you get good service.

Thats all for now, thanks for reading!

Andrew Degenhardt
ELAN COMMUNICATIONS