What I found Special in :ror=>

:dry=>

Don' Repeat Yourself: every piece of knowledge in a system should be expressed in just one place. Rails uses the power of Ruby to bring that to life. You’ll find very little duplication in a Rails application; you say what you need to say in one place a place often suggested
by the conventions of the MVC architecture—and then move on. For programmers used to other web frameworks, where a simple change to the schema could involve them in half a dozen or more code changes, this was a revelation.

:convention_over_configuration=>

It means that Rails has sensibledefaults for just about every aspect of knitting together your application.Follow the conventions, and you can write a Rails application using less codethan a typical Java web application uses in XML configuration. If you need tooverride the conventions, Rails makes that easy, too.

Developers coming to Rails found something else, too. Rails is new, and thecore team of developers understands the new Web. Rails isn’t playing catchupwith the new de facto web standards: it’s helping define them. And Rails makes it easy for developers to integrate features such as AJAX and RESTful
interfaces into their code: support is built in.

:rails_is_agile=>

Rails is all about individuals and interactions. There are no heavy toolsets,no complex configurations, and no elaborate processes. There are just small groups of developers, their favorite editors, and chunks of Ruby code. This leads to transparency; what the developers do is reflected immediately in what the customer sees. It’s an intrinsically interactive process.

:meta_programming=>

“programming your programming.”

Change the way you program in your programming language.
Program in a language designed for the problem you’re solving.

:method_missing=>

:validations=>