| |||||||||||||
Crossing borders: What's the secret sauce in Ruby on Rails? (developerWorks)Crossing borders: What's the secret sauce in Ruby on Rails? (developerWorks)Posted Oct 17, 2006 8:40 UTC (Tue) by tomsi (subscriber, #2306)In reply to: Crossing borders: What's the secret sauce in Ruby on Rails? (developerWorks) by ajross Parent article: Crossing borders: What's the secret sauce in Ruby on Rails? (developerWorks)
The deal with rails is to speed up development of certain a type of applications: those applications are web based and needs a database.
It contains a nice object/database wrapper called ActiveRecord, it uses to MVC pattern to make sure that your model and display stays separate, and it uses templates for presentation.
It has a "convention over configuration" philosophy. By shunning configruation files and forcing a specific way of creating database tables and field names, you get an application that is more self-documenting and easier to maintain (as there is only one way of doing things).
If this fits with your way of working and the problem you are trying to solve, it is great. And quick.
It is definitely worth a try.
Tom.
(Log in to post comments)
|
|||||||||||||